Vinay Sajip added the comment:
Closing, as documentation has now been updated.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18939
___
Vinay Sajip added the comment:
The venv documentation does assume that the reader knows what virtual
environments are and how they work. More details are available in PEP 405,
which is not referenced in this documentation - I will rectify that.
--
Roundup Robot added the comment:
New changeset ad09332f856f by Vinay Sajip in branch '3.3':
Issue #18939: Updated venv documentation with some clarifications.
http://hg.python.org/cpython/rev/ad09332f856f
New changeset 408b6b3dcf9a by Vinay Sajip in branch 'default':
Closes #18939: Merged
Graham Wideman added the comment:
@Vinay Sajip Thanks for looking at this issue and adding the link to PEP 405,
and your explanation When working... with helpful shebang comments.
That said, the combination of PEP 405 and this updated page doesn't clear
things up completely.
Vinay remarks
R. David Murray added the comment:
You have understood correctly, after reading the now-existing documentation.
Do you have a suggestion for how they could be further improved, given that
they currently seem to convey accurate information?
For the autonomy question, as far as I know the only
New submission from Graham Wideman:
http://docs.python.org/dev/library/venv.html
More detail needed regarding the original python environment
The article explains how to use venv to create a new python installation with
independent libraries etc, and a means to activate one or another virtual
Graham Wideman added the comment:
Additionally on the subject of venv docs: I would encourage making it more
clear regarding how activate changes the user's PATH. Both
http://www.python.org/dev/peps/pep-0405/ and
http://docs.python.org/3.3/library/venv.html talk about how activate adds the
R. David Murray added the comment:
Hmm. It seems to me that that document is indeed not clear as to what is
really going on. My understanding has always been that there is only one
Python interpreter, but that it behaves differently when invoked through the
symlink in the venv. I suppose
Graham Wideman added the comment:
Thanks R. David for your comments.
It should also mention that the activation is per-shell-session,
.. which also has implications (or lack of effect) for launching from Windows
Explorer, for example.
Seems like in practical use, one would need to set up a
