This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lac
Recipients docs@python, dstufft, eric.araujo, lac
Date 2015-09-17.14:13:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442499212.73.0.745656543772.issue25152@psf.upfronthosting.co.za>
In-reply-to
Content
https://docs.python.org/3/library/venv.html nowhere explicitly states
how you are supposed to get a venv with a particular python version.
Users of virtualenv will be looking for a -p option.

The doc says:

"Creation of virtual environments is done by executing the pyvenv script:"

which undoubtably works if you _have_ a pyenv script, but I don't have
one.  It is nowhere stated where I should find one.

Fortunately, I can also run things as

some_python_version -m venv myvenv 

This, everybody is able to do.  (However, it may not work, see
issue 25151 --  but forget that for now.)

This is something that everybody ought to be able to do.
Thus I propose either deleting the mention of pyenv, (if it is exactly
equivalent to running python -m venv)  or expanding
the section, indicating where the script lives, and why you might
want to run it instead of python -m venv.

Then, before the line:
The command, if run with -h, will show the available options:

add the line:

The version of python used in the venv is determined at this time.
If the default version of python is not the one desired, use:

/path/to/the/python/I/want -m venv  myenv instead.

(Plus, if there is a way to do this with pyenv, then list that
part here).
History
Date User Action Args
2015-09-17 14:13:32lacsetrecipients: + lac, eric.araujo, docs@python, dstufft
2015-09-17 14:13:32lacsetmessageid: <1442499212.73.0.745656543772.issue25152@psf.upfronthosting.co.za>
2015-09-17 14:13:32laclinkissue25152 messages
2015-09-17 14:13:31laccreate