pyvenv
was the recommended tool for creating virtual environments for
Python 3.3 and 3.4, and is deprecated in Python 3.6.
Changed in version 3.5: The use of venv
is now recommended for creating virtual environments.
========
"venv
accepts a new parameter --prompt
. This parameter provides an
alternative prefix for the virtual environment. (Proposed by Łukasz Balcerzak
and ported to 3.6 by Stéphane Wirtel in bpo-22829.)
Paul Moore <p.f.moore@gmail.com> wrote:
>
> > Well, not exactly. Do you do python -m venv, or py -x.x -m venv or
> > pythonx -m venv ? Wait, it's not installed by default on debian.
>
> Seriously? Debian don't provide venv in the standard Python install?
> That's just broken.
Frankly, I don't know where the current discussion comes from, but on
two recent Debian and Ubuntu setups, I get:
$ dpkg -S /usr/lib/python3.5/venv/__init__.py
libpython3.5-stdlib:amd64: /usr/lib/python3.5/venv/__init__.py
Which, for the uninitiated, means "the venv module is provided by the
Debian/Ubuntu package named libpython3.5-stdlib". That package is, in
turn, a dependency of the "python3.5" package.
Regards
Antoine.
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/