One more possible solution at Troubleshooting page
Open
Nobody has claimed this yet.
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Symptom Things to try pythongives me a “command not found” error or opens the Store app when I type it in my terminal.... pygives me a “command not found” error or opens the Store app when I type it in my terminal.... ... ... pipgives me a “command not found” error or opens the Store app when I type it in my terminal.... — at Python Setup and Usage > 4. Using Python on Windows > Troubleshooting
Here's one more possible reason for the symptoms above: the terminal just doesn't get PATH Variable updated (if PATH is modified when the terminal is still running).
And the respective solution is simple: Check PATH and reopen the terminal, then try again.
Linked PRs
- gh-143964
- gh-143981
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the Python Setup and Usage > Using Python on Windows > Troubleshooting page linked in the issue and review the existing symptom table. Compare the proposed PATH and terminal-restart guidance with linked PRs gh-143964 and gh-143981; the documentation is done when the agreed guidance appears in the troubleshooting page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100