summaryrefslogtreecommitdiffstats
path: root/Lib/venv/scripts/posix/activate.csh
Commit message (Collapse)AuthorAgeFilesLines
* gh-103088: Ensure POSIX venv scripts always use LF line endings (GH-103591)Steve Dower2023-04-171-0/+1
| | | Also touches the affected files in meaningless ways to ensure they get updated when pulling
* bpo-35328: Set VIRTUAL_ENV_PROMPT at venv activation (GH-21587)Zackery Spytz2020-07-281-1/+2
| | | Co-Authored-By: Baptiste Darthenay <baptiste.darthenay@gmail.com>
* bpo-37663: have venv activation scripts all consistently use __VENV_PROMPT__ ↵Brett Cannon2019-08-211-13/+1
| | | | | | | for prompt customization (GH-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).
* Issue #27895: Spelling fixes (Contributed by Ville Skyttä).Raymond Hettinger2016-08-301-1/+1
|
* Issue #15417: Add support for csh and fish in venv activation scripts.Andrew Svetlov2012-10-041-0/+37