[issue17480] pyvenv should be installed someplace more obvious on Windows

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue17480] pyvenv should be installed someplace more obvious on Windows

Jason R. Coombs added the comment: Nice! Linking to issue25427. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue17480] pyvenv should be installed someplace more obvious on Windows

Zachary Ware added the comment: With pyvenv removed from 3.8 and various other proposals in other issues for where scripts should be installed on Windows, I'm going to go ahead and close this. -- resolution: -> out of date stage: -> resolved status: open -> closed versions: +Python

[issue17480] pyvenv should be installed someplace more obvious on Windows

Zachary Ware added the comment: I think a pyvenv.exe would be overkill, but I think it would be reasonable to install the pyvenv script to \Scripts rather than \Tools\Scripts, possibly as both 'pyvenv.py' and 'pyvenv-X.Y.py'. Personally, I still prefer 'py -3 -m venv', but I understand the ar

[issue17480] pyvenv should be installed someplace more obvious on Windows

Steve Dower added the comment: That last message should have been on #20451 :) My thoughts on pyvenv are that it should be in Scripts\ if anywhere, but I'm not desperate to have it on PATH. I would rather not start putting more files alongside python.exe. -- _

[issue17480] pyvenv should be installed someplace more obvious on Windows

Steve Dower added the comment: Automatically quoting arguments is more complicated than simply concatenating quotes, unfortunately, and people are guaranteed to have come up with ways to make it work already. My vote is for leaving this alone and letting the higher level functions be more cle

[issue17480] pyvenv should be installed someplace more obvious on Windows

Mark Lawrence added the comment: Any thoughts from our Windows gurus? -- nosy: +BreamoreBoy, steve.dower, tim.golden, zach.ware type: -> enhancement versions: +Python 3.5 -Python 3.3 ___ Python tracker ___

[issue17480] pyvenv should be installed someplace more obvious on Windows

Piotr Dobrogost added the comment: I've just stumbled upon this issue after asking "Where is pyvenv script in Python 3 on Windows installed?" question at http://stackoverflow.com/q/1598/95735 "Perhaps Windows installs should include (alongside Python.exe) a pyvenv.exe that invokes venv fo

[issue17480] pyvenv should be installed someplace more obvious on Windows

Jason R. Coombs added the comment: The installers don't put anything on PATH by default. Activestate installers and my custom installers do put PythonNN and PythonNN\Scripts on the path. It's true that PythonNN\Scripts is the place that third-party command-line tools are installed. I don't bel

[issue17480] pyvenv should be installed someplace more obvious on Windows

Changes by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue17480] pyvenv should be installed someplace more obvious on Windows

Michael Foord added the comment: PythonNN\Scripts is the "normal" place for Python command line tools to be installed to. Does the installer not put this on the PATH for windows? -- nosy: +michael.foord ___ Python tracker

[issue17480] pyvenv should be installed someplace more obvious on Windows

New submission from Jason R. Coombs: On Windows, pyvenv.py is installed to PythonNN\Tools\Scripts, which I would generally recommend not be added to the system's or user's PATH. It would be nice if there were a Windows-friendly launcher that's available similar to what's available on Unix. For