You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are five activation scripts and they are all do things differently when it comes to prompt manipulation. Standardizing on one set of semantics would probably be good for consistency and so people know what to expect regardless of their shell.
bash: use __VENV_PROMPT__ if defined (which is nearly true; bpo-37661), else if virtual env in a directory named "__" (for some defunked software named Aspen; bpo-37660) then use "[dir]", else "(dir)"
Command Prompt: use __VENV_PROMPT__
csh: use __VENV_NAME__ if defined, else calculate name and use "[dir]"
fish: same as bash, except if not using __VENV_PROMPT__ then use white text on a blue background
So the variances/questions are:
Always use __VENV_PROMPT__ and don't bother testing? (bpo-37661 suggests we should, or else come up with a new way to tell whether a custom prompt was provided)
Always use colour regardless of whether the prompt is custom? (I vote "yes"; don't care about what the colours happen to be)
Parentheses or square brackets? (Due to bpo-37661 I vote for parentheses since that's what people are used to)
New changeset 48ede6b by Brett Cannon in branch 'master': bpo-37663: have venv activation scripts all consistently use __VENV_PROMPT__ for prompt customization (GH-14941) 48ede6b
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: