Remove support for Python 3.3 because of tox #38
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
`tox` explicitely removed support for Python 3.3 as part of their [3.0.0 release](https://tox.readthedocs.io/en/latest/changelog.html#id88) so it doesn't seems viable to keep this version in the support matrix.
|
I generally use a policy of descriptive version support. Once a python version is EOL, I am willing to drop it, but only if I need features from the next version for the code itself. It is a bit annoying how difficult it is to maintain old testing to make sure that we don't accidentally drop support for a version without correctly updating the metadata, though. |
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.
toxexplicitely removed support for Python 3.3 as part of their 3.0.0 release so it doesn't seems viable to keep this version in the support matrix as this is breaking the travis build.Not sure if it this change warrants a changelog entry. If it does, please let me know.