bpo-37663: have venv activation scripts all consistently use __VENV_PROMPT__ for prompt customization#14941
Merged
brettcannon merged 9 commits intopython:masterfrom Aug 21, 2019
Merged
Conversation
Member
Author
|
/cc @mental32 |
mental32
approved these changes
Jul 24, 2019
Contributor
mental32
left a comment
There was a problem hiding this comment.
Thanks for cc'ing :)
Changes look good to me!
I'm curious about the special casing of "aspen magic directories" would you know anything about these? the link seems to point to a broken site.
Also I noticed you made typo changes, can I assume that'd be alright to do? (in case I catch an issue that needs a patch and a tidy up)
Member
Author
|
@mental32 I have no clue about them and since the URL is dead and the site seems to now be a news site I figured it wasn't worth keeping the code around. And yes, you can always touch up typos and such in comments if you come across them while working on code. The only reason I touched up the punctuation for the whole fish file was it's small enough to not be horribly distracting in the PR. |
Member
Author
|
@vsajip any issues with this change? |
lisroach
pushed a commit
to lisroach/cpython
that referenced
this pull request
Sep 10, 2019
…ROMPT__ for prompt customization (pythonGH-14941) The activation scripts generated by venv were inconsistent in how they changed the shell's prompt. Some used `__VENV_PROMPT__` exclusively, some used `__VENV_PROMPT__` if it was set even though by default `__VENV_PROMPT__` is always set and the fallback matched the default, and one ignored `__VENV_PROMPT__` and used `__VENV_NAME__` instead (and even used a differing format to the default prompt). This change now has all activation scripts use `__VENV_PROMPT__` only and relies on the fact that venv sets that value by default. The color of the customization is also now set in fish to the blue from the Python logo for as hex color support is built into that shell (much like PowerShell where the built-in green color is used).
DinoV
pushed a commit
to DinoV/cpython
that referenced
this pull request
Jan 14, 2020
…ROMPT__ for prompt customization (pythonGH-14941) The activation scripts generated by venv were inconsistent in how they changed the shell's prompt. Some used `__VENV_PROMPT__` exclusively, some used `__VENV_PROMPT__` if it was set even though by default `__VENV_PROMPT__` is always set and the fallback matched the default, and one ignored `__VENV_PROMPT__` and used `__VENV_NAME__` instead (and even used a differing format to the default prompt). This change now has all activation scripts use `__VENV_PROMPT__` only and relies on the fact that venv sets that value by default. The color of the customization is also now set in fish to the blue from the Python logo for as hex color support is built into that shell (much like PowerShell where the built-in green color is used).
websurfer5
pushed a commit
to websurfer5/cpython
that referenced
this pull request
Jul 20, 2020
…ROMPT__ for prompt customization (pythonGH-14941) The activation scripts generated by venv were inconsistent in how they changed the shell's prompt. Some used `__VENV_PROMPT__` exclusively, some used `__VENV_PROMPT__` if it was set even though by default `__VENV_PROMPT__` is always set and the fallback matched the default, and one ignored `__VENV_PROMPT__` and used `__VENV_NAME__` instead (and even used a differing format to the default prompt). This change now has all activation scripts use `__VENV_PROMPT__` only and relies on the fact that venv sets that value by default. The color of the customization is also now set in fish to the blue from the Python logo for as hex color support is built into that shell (much like PowerShell where the built-in green color is used).
gentoo-bot
pushed a commit
to gentoo/cpython
that referenced
this pull request
Apr 9, 2025
…ROMPT__ for prompt customization (pythonGH-14941) The activation scripts generated by venv were inconsistent in how they changed the shell's prompt. Some used `__VENV_PROMPT__` exclusively, some used `__VENV_PROMPT__` if it was set even though by default `__VENV_PROMPT__` is always set and the fallback matched the default, and one ignored `__VENV_PROMPT__` and used `__VENV_NAME__` instead (and even used a differing format to the default prompt). This change now has all activation scripts use `__VENV_PROMPT__` only and relies on the fact that venv sets that value by default. The color of the customization is also now set in fish to the blue from the Python logo for as hex color support is built into that shell (much like PowerShell where the built-in green color is used).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The activation scripts generated by venv were inconsistent in how they changed the shell's prompt. Some used
__VENV_PROMPT__exclusively, some used__VENV_PROMPT__if it was set although by default__VENV_PROMPT__is always set and the fallback matched the default, and one ignored__VENV_PROMPT__and used__VENV_NAME__instead (and even used a differing format to the default prompt). This change now has all activation scripts use__VENV_PROMPT__only and relies on the fact that venv sets that value by default.The color of the customization is also now set in fish to the blue from the Python logo for as hex color support is built into that shell (much like PowerShell where the built-in green color is used).
https://bugs.python.org/issue37663