Allow to specify pip version via github URL in Docker/CI workflow
#28697
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
boring-cyborg
bot
added
area:dev-tools
area:production-image
Closed
potiuk
force-pushed
the
allow-github-url-installation-for-pip
branch
2 times, most recently
from
33c1a61
to
31f88a7
Compare
|
Would love to merge that one to be able to test |
uranusjr
reviewed
Jan 4, 2023
We've only supported to install `pip` from released packages with a version number, but since `pip` does not support RC candidates (as extensively discussed in pypa/pip#10882) we cannot use the release versions to do that. We still want to help `pip` maintainers and be able to test the versions they release as early as possible, so we add support to install `pip` in our toolchain from a GitHub URL. That will allow us to test new `pip` version as soon as designated branch of `pip` will contain something resembling a release candidate ready for testing.
potiuk
force-pushed
the
allow-github-url-installation-for-pip
branch
from
31f88a7
to
72added
Compare
uranusjr
approved these changes
Jan 5, 2023
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 12, 2023
…28697) We've only supported to install `pip` from released packages with a version number, but since `pip` does not support RC candidates (as extensively discussed in pypa/pip#10882) we cannot use the release versions to do that. We still want to help `pip` maintainers and be able to test the versions they release as early as possible, so we add support to install `pip` in our toolchain from a GitHub URL. That will allow us to test new `pip` version as soon as designated branch of `pip` will contain something resembling a release candidate ready for testing. (cherry picked from commit 6cbf9b6)
ephraimbuddy
added
the
changelog:skip
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.
We've only supported installing
pipfrom released packages with a version number, but sincepipdoes not support RC candidates (as extensively discussed in pypa/pip#10882) we cannot use thepipRC versions to do that.We still want to help
pipmaintainers and be able to test the versions they release as early as possible, so we add support to installpipin our toolchain from a GitHub URL.That will allow us to test new
pipversion as soon as designated branch ofpipwill contain something resembling a release candidate ready for testing.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.