Update docs for v0.17.x release; Reintroduce Py26 and Py33 compat#397
Merged
Conversation
jmadler
changed the title
Contributor
Author
|
Approved in email with @edschofield |
Contributor
|
I'm curious, what is the reason to re-add EOL Python 2.6 support? The decision to remove it was reviewed and approved in a previous PR. These versions are no longer receiving bug fixes, including for security issues. Python 2.6 went EOL on 2013-10-29 and on 2017-09-29. Removing support for EOL Pythons will reduce testing and maintenance resources. Removing Python 2.6 will allow removing certain compatibility shims. Using pypinfo, here are the PyPI download statistics for the last 30 days, showing low numbers for these EOL Pythons:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.