[issue41011] [venv] record which executable and command were used to create a virtual environment

[Vinay Sajip]

Vinay Sajip  added the comment:


New changeset f4e325c21d6d9c2bf70224dc69d707b226f87872 by andrei kulakov in 
branch 'main':
bpo-41011: venv -- add more variables to pyvenv.cfg (GH-30382)
https://github.com/python/cpython/commit/f4e325c21d6d9c2bf70224dc69d707b226f87872


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41011] [venv] record which executable and command were used to create a virtual environment

[Éric Araujo]

Change by Éric Araujo :


--
versions: +Python 3.11 -Python 3.10

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41011] [venv] record which executable and command were used to create a virtual environment

[Andrei Kulakov]

Change by Andrei Kulakov :


--
keywords: +patch
nosy: +andrei.avk
nosy_count: 2.0 -> 3.0
pull_requests: +28592
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/30382

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue41011] [venv] record which executable and command were used to create a virtual environment

[Brett Cannon]

New submission from Brett Cannon :

When a virtual environment is created, the resulting pyvenv.cfg specifies the 
directory which contained the Python executable and the version of Python (see 
https://github.com/python/cpython/blob/master/Lib/venv/__init__.py#L147). 
Unfortunately that may not be enough to work backwards to which binary was used 
to create the virtual environment.

My idea is to add an `executable` and `command` key to pyvenv.cfg which record 
the Python executable name and the command used to construct the virtual 
environment, respectively. The former would disambiguate which exact Python 
interpreter was used, and the `command` key could be used by e.g. virtualenv to 
record what was used to construct the virtual environment. That potentially 
could be used to make recreating a broken virtual environment easier.

--
components: Library (Lib)
messages: 371775
nosy: brett.cannon, vinay.sajip
priority: normal
severity: normal
status: open
title: [venv] record which executable and command were used to create a virtual 
environment
type: enhancement
versions: Python 3.10

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com