[issue15374] venv environment variable should follow the conventions

Changes by Antoine Pitrou : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue15374] venv environment variable should follow the conventions

Antoine Pitrou 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 overriding rea

[issue15374] venv environment variable should follow the conventions

Carl Meyer 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 overriding reason, it w

[issue15374] venv environment variable should follow the conventions

Vinay Sajip 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 be interested in Carl's

[issue15374] venv environment variable should follow the conventions

Antoine Pitrou 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 compatible

[issue15374] venv environment variable should follow the conventions

Vinay Sajip 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. -- ___ Python tracker

[issue15374] venv environment variable should follow the conventions

New submission from Antoine Pitrou : 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, since it would