Move get-pip.py warning above instructions to prevent accidental misuse #1953
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR moves the existing warning about using
get-pip.pyso that itappears before the installation steps.
Currently, the tutorial shows the instructions for downloading and running
get-pip.pybefore the cautionary note, which may lead beginners to runthe command without seeing the warning first. Since this tutorial is aimed at
new Python users, placing the warning earlier helps prevent accidental misuse.
No content was changed—only the order—keeping the diff minimal and focused.
📚 Documentation preview 📚: https://python-packaging-user-guide--1953.org.readthedocs.build/en/1953/