Repository navigation
Add support for Django 4.2 through 6 - #157
antidipyramid wants to merge 9 commits into
Conversation
|
Coverage is 98.902% — feature/django6-support into master. No base build found for |
|
Coverage is 98.902% — feature/django6-support into master. No base build found for |
hancush
left a comment
hancush
left a comment
There was a problem hiding this comment.
All right! Few things inline.
| license = "BSD-3-Clause" | ||
| license-files = ["LICENSE"] | ||
| requires-python = ">=3.10" | ||
| dependencies = ["Django>=4.2", "psycopg2-binary"] |
There was a problem hiding this comment.
Should we put an upper limit on Django? If we'll support the whole 6 series, let's do <7, otherwise cap it at 6.0. Can you also make sure the changelog is consistent with whatever 6 series support we're adding? Right now, it just says 6.0.
There was a problem hiding this comment.
Let's do an upper limit of <7. Django 6.2 is not out till next April but there shouldn't be any breaking changes. Also updated the changelog.
Also included tests for 6.1 in the workflow.
Co-authored-by: hannah cushman garland <hancush@users.noreply.github.com>
…g 7 & add 6.1 testing to workflow
Overview
This PR updates the supported version of Django to >=4.2 and <=6. It also updates the supported Python versions to >=3.10 and <=3.14
I also replaced
setup.pywith apyproject.tomlfile, which is now preferred.Notes
The biggest changes in this branch are relatively minor:
index_togetherwithmodels.Indexin models'Metamodels.NullBooleanFieldwithmodels.BooleanField(null=True, ...)