Drop support for end-of-life Pythons #164
Open
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.
Python 2.6 and 3.3 are end-of-life. They are no longer receiving bug fixes, including for security issues. Python 2.6 went EOL on 2013-10-29 and Python 3.3 on 2017-09-29. For additional details on supported Python versions, see:
Active branches: https://devguide.python.org/#status-of-python-branches
End-of-life branches: https://devguide.python.org/devcycle/#end-of-life-branches
Removing support for EOL Pythons will reduce testing and maintenance resources. For example, can begin moving towards a unified Python 2/3 version of pyinotify, reducing massive duplication.
Using pypinfo, here are the download statistic for the last 30 days, showing very low numbers for EOL Pythons.
Changes: