Python 2.6, 2.7, 3.2-3.6 in README.md, setup.py, and tox.ini#25
Merged
Conversation
added 3 commits
November 12, 2017 20:45
Why not drop support for Python versions that are already EOL such as 2.6, 3.2, and 3.3? * https://docs.python.org/devguide/index.html#branchstatus
Contributor
|
Looks good to me. |
Owner
|
Hey sorry for the incredibly late reply. The changes you made are fine, I'll merge them in. I don't want to drop support for python 2.6, compatibility was the main reason this project was created in the first place (well, I was bored too and reading the pystache code was painful). |
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
4 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.
Why not drop support for Python versions that are already EOL such as 2.6, 3.2, and 3.3?