Drop support for Python<3.5, Django<2.2, pytest<5.4 #869
Conversation
This file contains hidden or 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
bluetech
force-pushed
the
version-4
branch
6 times, most recently
from
0690486 to
849707e
Compare
|
🎉 finally got the CI to pass with all the changes... |
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.
This is my proposal for version 4.0.0 of the plugin, per issue #868. The idea is to have a clean slate for further development in 4.0.0 by dropping support for unsupported Python, Django and pytest versions. Development for the 3.x series can continue on a separate branch if such need arises.
After this is merged I intend to also switch CI from Travis to github actions.
Closes #763.
Closes #796.
Closes #744.
Closes #660.