Antoine Pitrou pit...@free.fr added the comment:
Yes, there are a number of third-party utility packages (and many,
many e.g. personal custom bash prompts) that check the value of the
$VIRTUAL_ENV variable to detect whether one is currently active, and
display its name. Unless there's an
Changes by Antoine Pitrou pit...@free.fr:
--
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15374
___
New submission from Antoine Pitrou pit...@free.fr:
pyvenv's environment variable is currently named VIRTUAL_ENV (it seems).
It would be better if it followed the trend of other Python environment
variables such as PYTHONHOME, PYTHONSTARTUP, etc.
(so, PYTHONVENV ?)
Setting as deferred blocker,
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
This name was picked because the virtualenv tool uses it, and keeping the name
allows any existing third-party projects and scripts which use it to require
minimal, if any, changes.
--
___
Antoine Pitrou pit...@free.fr added the comment:
This name was picked because the virtualenv tool uses it, and keeping
the name allows any existing third-party projects and scripts which
use it to require minimal, if any, changes.
Which means that these third-party projects are automatically
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Which means that these third-party projects are automatically
compatible with pyvenv?
I can't speak for them, but it's one less thing for people to have to change.
The intention certainly was to minimise friction in this area.
I would
Carl Meyer c...@dirtcircle.com added the comment:
Yes, there are a number of third-party utility packages (and many, many e.g.
personal custom bash prompts) that check the value of the $VIRTUAL_ENV variable
to detect whether one is currently active, and display its name. Unless there's
an
