See my question here
https://groups.google.com/forum/#!topic/comp.lang.python/BUmyc_hzAsA
In particular Carl Meyer's response
https://groups.google.com/d/msg/comp.lang.python/BUmyc_hzAsA/-cT-N-g_LL4J

I am not sure what is possible with venv but I would suggest that the statement 'allowing creation of environments with various Python versions' needs to be clarified and / or altered.

Thanks
Graham

See also
https://groups.google.com/d/msg/comp.lang.python/BUmyc_hzAsA/Nx5QgT1gzYEJ

Hmm.  We don't in general mention 2.7 in the python3 docs (in fact I found only one mention of it, in the logging package docs).  I suppose this might be confusing enough to warrant it.  But it might be better to rewrite that sentence to make it clear that the python binary you get in your virtual environment is the one that the venv command comes from.  That should make it pretty clear you can't use it with 2.7, since 2.7 doesn't include venv.

ok current version
Each virtual environment has its own Python binary (allowing creation of environments with various Python versions) and can have its own independent set of installed Python packages in its site directories.

Suggested Alternative
Each virtual environment has its own isolated Python binary (which matches the version used to create it) and can have its own independent set of installed Python packages in its site directories.

Current version
Each virtual environment has its own Python binary (allowing creation of environments with various Python versions) and can have its own independent set of installed Python packages in its site directories.

Another suggested revision
Since its introduction in Python 3.3, venv may be used to create a virtual environment with its own Python binary and optionally its own independent set of installed Python packages in its site directories. Multiple virtual environments permit various Python versions to exist on a system.

David and Graham,
Perhaps moving the "see also" box (see also Python Packaging User Guide: Creating and using virtual environments) closer to the top, perhaps under the pep reference, would be helpful for the user.

Virtual environments are confusing for those new to Python since there are many "env"s such as venv, pyvenv, virtualenv, virtualenvwrapper, pyenv tool, and myenv used in many examples.

Carol

I think Graham's formulation provides more information.  venv already has a "new in python 3.3" at the top (just before that sentence), so putting that in the text feels redundant.

On the other hand, the current placement of the 'see also' box looks odd, unless the packaging authority doesn't mention virtual environments on Windows (and if it doesn't, it should!).  I agree that moving that up to just after the PEP reference is probably a good idea.

David,

Sounds good to me. I'll submit a patch with Graham's suggested text and move the See also box up right after the PEP reference.

Thanks,
Carol

See also the recent addition of a section on venv to the Tutorial section of the docs (Doc/tutorial/venv.rst, issue23891). The wording there and in the module docs should at least be consistent with each other.

New changeset 50326927465c3f5c6c0168fc43310c8e97db0a47 by Steve Dower (Elena Oat) in branch 'master':
bpo-24356: Specify which Python binary will be used with venv (GH-6589)
https://github.com/python/cpython/commit/50326927465c3f5c6c0168fc43310c8e97db0a47

New changeset 83b449d754f4da3be107b508392ef5180f105c8b by Steve Dower in branch '3.7':
bpo-24356: Specify which Python binary will be used with venv (GH-6589)
https://github.com/python/cpython/commit/83b449d754f4da3be107b508392ef5180f105c8b