Upgrade to pex 1.5.1; ~kill --resolver-blacklist. #6619
Merged
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
PEX now handles blacklisting for us by respecting PEP-508 enviornment markers. Fixes pantsbuild#5696
There was a problem hiding this comment.
Very cool change!
I remember how much confusion we had at Foursquare figuring out how to setup a blacklist, until you all in Slack mentioned this option. So, this consolidation with standard Python conventions is great to see.
cc @mateor - no need to review, but so you're aware of this change when Foursquare upgrades Pants again.
Eric-Arellano
approved these changes
Oct 11, 2018
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.
PEX now handles blacklisting for us by respecting PEP-508 enviornment
markers.
Fixes #5696