If you look at https://github.com/python/cpython/blob/master/Lib/venv/__init__.py#L112-L113 you will see that the prompt context for a virtual environment is always set. Then if you look at the string substitutions for the activation scripts you will also see that the string substitution for __VENV_PROMPT__ is thus always done.

This is an issue as it means that for the fish and bash activation scripts they have erroneous checks for custom prompts. I.e. https://github.com/python/cpython/blob/master/Lib/venv/scripts/posix/activate.fish#L55 for fish and https://github.com/python/cpython/blob/master/Lib/venv/scripts/common/activate#L57 for bash will never fail, halting any other further checks unless one creates a custom EnvBuilder class which will make sure the prompt context stays empty all the way to string substitution. This impacts the colouring of the prompt in fish as that's only done if there is no default prompt (which is never true).

Brett, Vinay: mind if I handle this one? I'm looking for a good first issue to tackle.

In terms of solutions I propose adding short circuiting logic to the checks for custom prompts to test against the default case `({context.env_name})`

I've added a PR (#1492) since it was a simple fix.

Please feel free to reject if this issue is reserved or some other fatal issue with the solution is found.

Otherwise I'd love a review and a double check (mainly paranoia from not wanting to mess up).

Fixed by issue37663.