docs: cut the update section down to three commands - #5
Merged
Conversation
It had grown a collapsible essay on how pip resolves git URLs, a --force-reinstall workaround, and a @ref pinning example. All of that existed to route around one bug: the version never moved, so --upgrade did nothing. 0.2.0 fixed that. Verified end to end from a stale 0.1.0 environment -- plain `pip install --upgrade` now uninstalls 0.1.0 and installs 0.2.0. The workaround it worked around no longer applies, so it is gone rather than left standing as folklore. What is left is the three things someone actually asks: update it, find it, remove it. `pip show -f` answers "where is it" and "which version" in one command instead of two. Each was run verbatim against a real install before being written down.
A natural thing to wonder, and leaving it unsaid invites a second section that would duplicate the first. The commands are identical; the only difference is WHICH installation they act on, which makes activation the step that matters and `pip show -f` the way to check. Verified: the same `pip show -f` reports the venv path when activated and "not found" when not.
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.
The update section had grown a collapsible essay on how pip resolves git URLs, a
--force-reinstallworkaround, and a@refpinning example.All of it existed to route around one bug: the version never moved, so
--upgradedidnothing. #4 fixed that. Verified end to end from a stale
0.1.0environment — plainpip install --upgradenow uninstalls0.1.0and installs0.2.0.So the workaround no longer applies, and it is deleted rather than left standing as folklore
someone repeats for years.
What is left is the three things people actually ask:
pip show -fanswers "where is it installed" and "which version do I have" in one commandinstead of two. Each was run verbatim against a real install before being written down.
134 passed, 4 skipped.