Bump to future==0.17.1 #7159
Merged
Bump to future==0.17.1 #7159
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
Eric-Arellano
approved these changes
Jan 25, 2019
|
You'll have to merge master to get the contrib tests to pass. |
stuhood
force-pushed
the
stuhood/most-futuristic-future
branch
2 times, most recently
from
ac816f0
to
2a79083
Compare
stuhood
force-pushed
the
stuhood/most-futuristic-future
branch
from
2a79083
to
1015452
Compare
|
You'll only get one win here. The package is an sdist - so pex will need to build it into a wheel and the sdist doesn't contain the universal flag, so it will build for 2 or 3 depending on the interpreter being used to pex things up. |
|
The second win will come from a fix for pex-tool/pex#415 |
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.
Problem
future==0.16.0cannot be resolved in the context oflinux_x86_64-cp-36-cp36m(see the subtext of #7158), and it seems likely thatfuture==0.17.1can be, since its pypi entry claims compatibility with python 3.6. Either way, updating to the most recent version seems win-win.Solution
Update to
future==0.17.1.