[issue25154] Drop the pyvenv script

Eric V. Smith added the comment: There's a typo here in 'executable': + '`{} -m venv`'.format(exeutable), file=sys.stderr) And this could now be: print('WARNING: the pyenv script is deprecated in favour of ' f'`{executable} -m venv`', file=sys.stderr) ! And since there

[issue25154] Drop the pyvenv script

Brett Cannon added the comment: Took Eric's advice in 8828d7847e92 as well as actually tested the results this time. :P -- status: open -> closed ___ Python tracker

[issue25154] Drop the pyvenv script

Changes by Brett Cannon : -- status: closed -> open ___ Python tracker ___ ___

[issue25154] Drop the pyvenv script

Brett Cannon added the comment: Sorry for the delay on this; fell ill Friday and then had guests all weekend. -- status: open -> closed ___ Python tracker

[issue25154] Drop the pyvenv script

Roundup Robot added the comment: New changeset 7a5f8418b4ab by Brett Cannon in branch 'default': Issue #25154: Make the file argument apply to the print function and https://hg.python.org/cpython/rev/7a5f8418b4ab -- ___ Python tracker

[issue25154] Drop the pyvenv script

Stefan Behnel added the comment: May I ask how difficult it is for any of the core developers to fix a known typo in a Python source file? -- nosy: +scoder ___ Python tracker

[issue25154] Drop the pyvenv script

Ezio Melotti added the comment: Fixing a typo is trivial. If the typo affects several version the changeset needs to be merged on all the applicable branches before being pushed. -- nosy: +ezio.melotti ___ Python tracker

[issue25154] Drop the pyvenv script

Antoine Pitrou added the comment: Did you fix the "exeutable" typo? -- nosy: +pitrou ___ Python tracker ___

[issue25154] Drop the pyvenv script

Brett Cannon added the comment: Not yet. I will get to it no later than Friday (just a matter of either remembering to quickly fix it when I get home from work, bother setting up SSH keys at work, or simply doing it on Friday when I typically do all of my Python work). --

[issue25154] Drop the pyvenv script

Brett Cannon added the comment: I have a typo in my commit where I accidentally placed the file argument in str.format() instead of for print() (pointed out on GitHub). -- status: closed -> open ___ Python tracker

[issue25154] Drop the pyvenv script

Changes by Brett Cannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue25154] Drop the pyvenv script

Roundup Robot added the comment: New changeset 6ab285820db2 by Brett Cannon in branch 'default': Issue #25154: Deprecate the pyvenv script. https://hg.python.org/cpython/rev/6ab285820db2 -- nosy: +python-dev ___ Python tracker

[issue25154] Drop the pyvenv script

Brett Cannon added the comment: Here is a patch that adds a message to stderr about the deprecation. -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file40579/issue25154.diff ___ Python tracker

[issue25154] Drop the pyvenv script

Remi Pointel added the comment: I would prefer to keep this script with the version referring to the version of python used (pyvenv-3.4, pyvenv-3.5, ...). -- nosy: +rpointel ___ Python tracker

[issue25154] Drop the pyvenv script

Brett Cannon added the comment: python-dev did not seem to object to the idea. -- assignee: -> brett.cannon ___ Python tracker ___

[issue25154] Drop the pyvenv script

Barry A. Warsaw added the comment: I have a patch which will at least improve the error message when `python3 -m venv` fails because python3-venv isn't installed on Debian/Ubuntu. I will work with Doko on this. -- ___ Python tracker

[issue25154] Drop the pyvenv script

New submission from Brett Cannon: I propose that the pyvenv script be deprecated in Python 3.5 and removed in Python 3.8. The reason for this proposal is because it is non-obvious what version of Python a pyvenv command is tied to (heck, it isn't necessarily obvious that it's Python 3). There

[issue25154] Drop the pyvenv script

Barry A. Warsaw added the comment: I'm sympathetic, given that in Debian/Ubuntu (and maybe other distros) where we have both Python 3.4 and 3.5, we have to install /usr/bin/pyvenv-3.4 and pyvenv-3.5, and then use symlinks to provide the default version. --

[issue25154] Drop the pyvenv script

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list

[issue25154] Drop the pyvenv script

Laura Creighton added the comment: Due to debian policy decision https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732703 neither pyenv nor python -m venv may work for you. While things are getting changed, it would be good if people running into this problem got a better error message than:

[issue25154] Drop the pyvenv script

Brett Cannon added the comment: the ensurepip case is another issue, so if you want you can file a separate issue for it so it doesn't get lost. -- ___ Python tracker

[issue25154] Drop the pyvenv script

Changes by Barry A. Warsaw : -- nosy: +doko ___ Python tracker ___ ___ Python-bugs-list