New resolver constraint markers #8727
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
uranusjr
force-pushed
the
new-resolver-constraint-markers
branch
from
b277846
to
4683ad0
Compare
|
CI ain't happy. |
|
LGTM, but CI needs fixing. Ping me to review when the CI is working, and I'll approve then (just in case fixing the CI adds extra complexity...). |
|
Looks like PyPI had some availability issues. Rerunning. |
pradyunsg
approved these changes
Aug 7, 2020
|
Merged since Paul already OK'ed this change, and no additional changes were made. :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fix #8724. That’s easier than I expected 🙂