This doesn't install pip or uv to my path, which makes it useless for my purposes #222
Closed as duplicate
Description
>pip 'pip' is not recognized as an internal or external command, operable program or batch file. >uv 'uv' is not recognized as an internal or external command, operable program or batch file.
of course, py -m pip works, but who cares? I'm trying to use projects that just call pip (etc).
Activity
zooba commented on Nov 18, 2025
Sorry to hear that. Perhaps you should install uv instead?
hr-sbu commented on Jan 5, 2026
Hi there,
I just came to report this exact issue.
While the old installer would put pip into PATH, the new one doesn't.
This cannot be right – PEP 773 stated "most users want a “one-click” (or fewer) install", and pip is probably one of the most important tools to have, so I'm quite confident that this change was not intended.
My expectations was: the launcher/installer should add the site-packages executables to PATH, too, or at least provide instructions to me on how to achieve that – as the pip.exe is now somewhat buried somewhere in AppData, pretty inconvenient to find.
hr-sbu commented on Jan 5, 2026
seems #140 has this one already covered?
edit: and #121 ...
zooba commented on Jan 14, 2026
This is true, but it shouldn't really be used outside of a virtual environment. If you py -m venv ... to create one1 and then activate it, you'll get a pip command.
Globally installing packages is an anti-pattern that we think people should mostly avoid doing.
That said, #121 does indeed "fix" this, so users will start getting more commands on their PATH when they install packages that expose them. We'll see how popular that turns out to be...
Footnotes
And this is the only supported command for it - the pyvenv command was removed years ago. ↩