On 18 September 2015 at 05:04, Barry Warsaw <ba...@python.org> wrote: > On Sep 17, 2015, at 06:40 PM, Brett Cannon wrote: > >>I propose that the pyvenv script be deprecated in Python 3.5.1 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). > > That's why in Debian/Ubuntu we include /usr/bin/pyvenv-X.Y for all supported > versions (currently 3.4 and 3.5 in Ubuntu 15.10), and then symlink > /usr/bin/pyvenv to the default one. So I'm sympathetic to this proposal.
I currently use pyvenv directly, but I agree with starting a migration to only supporting the more explicit "python -m venv". There's always an inherent ambiguity on *nix with unqualified version sensitive Python commands as to whether they're referring to Python 2 or 3, as the answer often depends on *how old* the particular script is (e.g. pip and virtualenv relate to the Python 2 installation, while pyvenv relates to the Python 3 installation). There's one slightly oddity in the migration, which is that "pyvenv" will still run even if you're in an activated Python 2 virtual environment, while "python -m venv" fails. The answer is to use a qualified Python version in the latter call. I assume the change to the script will include forcing that particular deprecation warning to be visible by default. Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
