This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Expose venv --prompt value to an environment value
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 3.8
Status: closed Resolution: duplicate
Dependencies: Superseder:
Assigned To: Nosy List: Tomer, vinay.sajip, xtreak
Priority: normal Keywords:

Created on 2018-08-20 10:20 by Tomer, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (3)
msg323782 - (view) Author: Tomer Keren (Tomer) Date: 2018-08-20 10:20
In the same way the $VIRTUAL_ENV variable tells the virtual environment directory, A variable such as $VENV_NAME or $VENV_PROMPT should tell the value given to the venv `--prompt` option (Introduced in Issue22829).

An individual could override the EnvBuilder class like the docs say, but that wouldn't insure any user will have the variable set. This is crucial for usage in custom libraries that want to display the given prompt.
msg333042 - (view) Author: Karthikeyan Singaravelan (xtreak) * (Python committer) Date: 2019-01-05 05:38
issue35328 seems like a related issue with a PR that sets VIRTUAL_ENV_PROMPT. Also see issue35661 to store the venv prompt in config file.
msg333132 - (view) Author: Vinay Sajip (vinay.sajip) * (Python committer) Date: 2019-01-07 03:35
Duplicate of bpo-35328, which has a PR.
Date User Action Args
2022-04-11 14:59:04adminsetgithub: 78620
2019-01-07 03:35:06vinay.sajipsetstatus: open -> closed

nosy: + vinay.sajip
messages: + msg333132

resolution: duplicate
stage: resolved
2019-01-05 05:38:13xtreaksetnosy: + xtreak

messages: + msg333042
versions: - Python 3.5, Python 3.6, Python 3.7
2018-08-20 10:20:50Tomercreate