-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add section clarifying pip version support #11556
Merged
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
# Why ------------------------------------------------------ Since pip is a widely used library by the python community, it would be nice to have some formal documentation out there making clear what versions are supported. # What these changes do ----------------------------------------------------- Adds a section to the release-process page titled Supported Versions, along with language making clear that the latest major version of pip is the only supported version. It also encourages folks make regular updates. See also: GH issue 11549, pypa#11549
1 task
pfmoore
requested changes
Oct 27, 2022
Co-authored-by: Paul Moore <[email protected]>
Co-authored-by: Paul Moore <[email protected]>
Co-authored-by: Paul Moore <[email protected]>
pfmoore
approved these changes
Oct 27, 2022
pfmoore
added
the
skip news
Does not need a NEWS file entry (eg: trivial changes)
label
Oct 27, 2022
@pypa/pip-committers Does anyone else have any problem with this? This has always been our policy and I see no reason not to document it. Assuming no-one objects, I'll merge this (probably tomorrow). |
pradyunsg
reviewed
Oct 27, 2022
hollabaq86
commented
Oct 27, 2022
pradyunsg
approved these changes
Oct 27, 2022
Reverts are cheap so... I'm gonna eagerly squash-merge this. If someone has concerns, we can iterate on this. :) |
Thanks for the contribution, @hollabaq86! |
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.
Why
Since pip is a widely used library by the python community, it would be nice to have some formal documentation out there making clear what versions are supported.
What these changes do
Adds a section to the release-process page titled Supported Versions, along with language making clear that the latest major version of pip is the only supported version. It also encourages folks make regular updates.
Other considerations:
Since this is a documentation update, I wasn't sure if this warrants a news file. If folks feel its warranted please let me know and I'll add that to this PR!
See also:
GH issue 11549