Ah, I see it now, thanks.On Mon, Nov 13, 2017 at 10:29 AM, Nick Coghlan <firstname.lastname@example.org> wrote:
> On 13 November 2017 at 07:11, Chris Angelico <email@example.com> wrote:
>> On Mon, Nov 13, 2017 at 6:24 AM, Stephan Houben <firstname.lastname@example.org> 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.
>>> 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
>>> 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:
>> 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
> I think the deprecation notice for pyvenv should just be deleted,
> since it renders like the *module* is deprecated.
Agreed; or maybe downgrade it to a parenthetical comment. Focus on
"this is how to do the obvious thing", and only as an afterthought
mention "it used to be done differently" in case someone greps for
Python-ideas mailing list
Code of Conduct: http://python.org/psf/