Export __VENV_PROMPT__ as environment variable

[lysnikolaou]

BPO	36966
Nosy	@lysnikolaou, @tirkarthi
Superseder	bpo-35328: Set a environment variable for venv prompt

^{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:

assignee = None
closed_at = <Date 2019-05-19.14:25:01.576>
created_at = <Date 2019-05-19.14:18:38.965>
labels = ['3.8', 'type-feature', 'library']
title = 'Export __VENV_PROMPT__ as environment variable'
updated_at = <Date 2019-05-19.14:25:41.433>
user = 'https://github.com/lysnikolaou'

bugs.python.org fields:

activity = <Date 2019-05-19.14:25:41.433>
actor = 'xtreak'
assignee = 'none'
closed = True
closed_date = <Date 2019-05-19.14:25:01.576>
closer = 'lys.nikolaou'
components = ['Library (Lib)']
creation = <Date 2019-05-19.14:18:38.965>
creator = 'lys.nikolaou'
dependencies = []
files = []
hgrepos = []
issue_num = 36966
keywords = []
message_count = 3.0
messages = ['342855', '342856', '342858']
nosy_count = 2.0
nosy_names = ['lys.nikolaou', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '35328'
type = 'enhancement'
url = 'https://bugs.python.org/issue36966'
versions = ['Python 3.8']

[lysnikolaou]

For those, who use custom tools for their terminals, prepending __VENV_PROMPT__ to PS1 doesn't really help all that much, because it gets overwritten by those tools. Would it make sense to export __VENV_PROMPT__ as an environment variable upon activation, so that these tools can make use of it, in order to edit PS1 accordingly?

[tirkarthi]

Is this same as bpo-35328?

[lysnikolaou]

It is. Somehow search failed me big time. I'm closing the issue.