Recommend uv standalone installer over pip install uv on Windows#43
Merged
Conversation
pip install uv puts uv.exe in a Python Scripts directory that's often missing from PATH, so the command silently fails to resolve right after install even though the pip install itself succeeded. Astral's own installer configures PATH automatically. Switches the setup guide to it and adds a troubleshooting entry for anyone who already hit the pip-installed version not being found. Also points two stale Task Scheduler links at docs/WINDOWS_SCHEDULING.md instead of the README anchor now that section only summarizes and redirects. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
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.
Summary
pip install uvto Astral's standalone PowerShell installer, based on a real setup failure:pip install uvsucceeds but theuvcommand isn't recognized afterward becauseuv.exelands in a Python Scripts directory that's often missing from PATH.Test plan