| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Sorry, something went wrong.
|
|
||
| By default, the scripts ``pipX`` and ``pipX.Y`` will be installed (where | ||
| X.Y stands for the version of Python used to invoke ``ensurepip``). The | ||
| By default, the scripts ``pipN`` and ``pipN.Y`` will be installed (where |
There was a problem hiding this comment.
Maybe pipN.M?
Sorry, something went wrong.
There was a problem hiding this comment.
Why change this at all? pipX.Y is the normal convention here, used in the pip documentation.
Sorry, something went wrong.
There was a problem hiding this comment.
Ok, this change is unrelated anyway and no users complained about it. I agree with @pfmoore
Sorry, something went wrong.
There was a problem hiding this comment.
Please leave the pipX.Y naming convention unchanged.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
Sorry I hadn’t seen the comment by @sobolevn regarding the pipx application. Nevertheless, I disagree - the pipX.Y convention is well established, and consistency with existing terminology is important. |
Sorry, something went wrong.
|
I have made the requested changes; please review again. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @pfmoore: please review the changes made to this pull request. |
Sorry, something went wrong.
|
Thanks! LGTM. |
Sorry, something went wrong.
|
We usually backport doc changes, should we in this case? |
Sorry, something went wrong.
|
Thanks @Mr-Sunglasses for the PR, and @pfmoore for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
|
Thanks @Mr-Sunglasses for the PR, and @pfmoore for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry, something went wrong.
…pip` CLI (pythongh-130253) (cherry picked from commit 8cd7f8b) Co-authored-by: Kanishk Pachauri <itskanishkp.py@gmail.com>
|
GH-130258 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
…pip` CLI (pythongh-130253) (cherry picked from commit 8cd7f8b) Co-authored-by: Kanishk Pachauri <itskanishkp.py@gmail.com>
|
GH-130259 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
I don't know the policy for doc changes, but if that's the usual approach, I see no reason not to. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
fix: #130160
📚 Documentation preview 📚: https://cpython-previews--130253.org.readthedocs.build/