[issue37663] Making venv activation script prompts consistent

Change by Brett Cannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue37663] Making venv activation script prompts consistent

Brett Cannon added the comment: New changeset 48ede6b8f685669f53d26ae8456647af42ae3dae by Brett Cannon in branch 'master': bpo-37663: have venv activation scripts all consistently use __VENV_PROMPT__ for prompt customization (GH-14941) https://github.com/python/cpython/commit/48ede6b8f685669

[issue37663] Making venv activation script prompts consistent

Change by Brett Cannon : -- keywords: +patch pull_requests: +14713 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14941 ___ Python tracker ___ ___

[issue37663] Making venv activation script prompts consistent

Change by Brett Cannon : -- dependencies: +Drop support for Aspen magic directories in venv's activate scripts, venv activation scripts erroneously check if __VENV_PROMPT__ is defined ___ Python tracker

[issue37663] Making venv activation script prompts consistent

New submission from Brett Cannon : 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. Currentl

[issue37663] Making venv activation script prompts consistent

Change by Brett Cannon : -- priority: normal -> low ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m