pip: 20.3.4 -> 21.0.1 #1
Closed
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
…setup_file' as it's a no-op now (bazel-contrib#393)
This fixes the same issue as bazel-contrib#232 but in another place. Co-authored-by: Jonathon Belotti <[email protected]>
Support binary wheels Also allow other Python tag specifiers like cp35, to constrain to a particular Python version.
13 tasks
…irectory (bazel-contrib#336) If in a dependency tree a directory is used as out this is passed as input_file to wheelmaker which then generates an unhandled error as it tries to write the directory as a file. Co-authored-by: Jonathon Belotti <[email protected]>
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.
PR Checklist
Please check if your PR fulfills the following requirements:
.parfiles. See CONTRIBUTING.md for infoPR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Follow up to bazel-contrib#405
This PR introduces pip 21.0.1 as the vendored version of pip. This version of pip will only support Python 3+ and is pip breaking away from Python 2 support since pip 21.0: https://pip.pypa.io/en/stable/news/#id1
My suggestion would be to first merge bazel-contrib#405 and prepare a release or tag along with documentation around the
pip_installPython 2 support. Then this PR can be rebased against upstream bazelbuild/rules_python and merged to support Python 3pip_jnstallsupport only for future development.Does this PR introduce a breaking change?
Other information