On 13 November 2017 at 09:29, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 13 November 2017 at 07:11, Chris Angelico <rosuav@gmail.com> wrote:
On Mon, Nov 13, 2017 at 6:24 AM, Stephan Houben <stephanh42@gmail.com> wrote:
Hi Antoine,
The venv module is included, however the pyvenv script is in a separate package python3.5-venv .
By the way, I was totally confused by the following text form the doc.
https://docs.python.org/3/library/venv.html
======== Deprecated since version 3.6: 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.
========
Not sure where you're reading that. I'm seeing:
""" Note The pyvenv script has been deprecated as of Python 3.6 in favor of using python3 -m venv to help prevent any potential confusion as to which Python interpreter a virtual environment will be based on. """
I think that's pretty clear. "python3 -m venv env" is the standard and recommended way to spin up a virtual environment.
It's further down in the page, under https://docs.python.org/3/library/venv.html#creating-virtual-environments
I think the deprecation notice for pyvenv should just be deleted, since it renders like the *module* is deprecated.
That is, the confusing one starting with "Deprecated since version 3.6: ...". The note Chris quoted is fine, and should be kept. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia