End support for py3.3? #1175
Merged
End support for py3.3? #1175
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
|
Python 3.6.0 is scheduled for final release on Friday. Is conda-forge building packages for it yet? If so, perhaps we just replace 3.3 with 3.6? |
|
Yes we should add a 3.6 env. Not sure if it's on conda-forge yet. |
|
Sounds good to me! |
shoyer
approved these changes
Dec 21, 2016
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.
Even at the beginning of this year its downloads were 90% lower than 2.6: https://hynek.me/articles/python3-2016/
Impetus is that pytest no longer supports it, and some of the tests I recently wrote don't work on 3.3