Add Django 4.0 support, drop Python 3.6 and Django 3.1 #208
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* runtests_urls.py had an issue from using pre-Django 2.2 import of urls * tox.ini forgot to remove 3.7 from Django 4.0 env
Pull Request Test Coverage Report for Build 1551681267
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add support for Django 4.0, drop support for Python 3.6 as it's near its EOL. Finally, dropping Django 3.1.
Fixes #207
Rationale
Python 3.6 isn't even supported for Django 4.0 (note, Django 4.0 uses the walrus operator!). Also, Python versions typically don't have an effect on cachalot. Django 3.1 -> Django 3.2 support has been a wild ride in the open-source community, but it seems stable now.