[issue19139] In venv, __VENV_NAME__ is the prompt, not the name

2013-10-02 Thread Roundup Robot
Roundup Robot added the comment: New changeset 7f913c6ada03 by Vinay Sajip in branch 'default': Closes #19139: Changed usage of __VENV_NAME__ and added __VENV_PROMPT__. http://hg.python.org/cpython/rev/7f913c6ada03 -- nosy: +python-dev resolution: - fixed stage: - committed/rejected

[issue19139] In venv, __VENV_NAME__ is the prompt, not the name

2013-10-01 Thread Paul Moore
New submission from Paul Moore: The documentation for venv states that __VENV_NAME__ in scripts is replaced by the name of the virtualenv. In fact, it is replaced by context.prompt, which is the prompt, rather than the name. The various activate scripts are not consistent with this behaviour.

[issue19139] In venv, __VENV_NAME__ is the prompt, not the name

2013-10-01 Thread Vinay Sajip
Vinay Sajip added the comment: Makes sense to me. Adding Carl Meyer to nosy, to see if he has a different view. -- nosy: +carljm ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19139 ___

[issue19139] In venv, __VENV_NAME__ is the prompt, not the name

2013-10-01 Thread Carl Meyer
Carl Meyer added the comment: Makes sense to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19139 ___ ___ Python-bugs-list mailing list

[issue19139] In venv, __VENV_NAME__ is the prompt, not the name

2013-10-01 Thread Paul Moore
Paul Moore added the comment: Cool. Patch attached (this fixes __VENV_NAME__ and implements __VENV_PROMPT__) -- keywords: +patch Added file: http://bugs.python.org/file31938/venv_prompt.patch ___ Python tracker rep...@bugs.python.org