New submission from Albert Cervin :
When creating a virtualenv using venv.EnvBuilder, it always uses
sys._base_executable. However, in some embedded cases (Blender being one
example), it is not set to a valid Python executable. The proposal is to add a
keyword parameter to the EnvBuilder constructor for specifying which python
interpreter to use, much like the -p flag in virtualenv.
--
components: Library (Lib)
messages: 375293
nosy: abbec
priority: normal
severity: normal
status: open
title: Allow customizing python interpreter in venv.EnvBuilder
type: enhancement
versions: Python 3.10, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python
3.9
___
Python tracker
<https://bugs.python.org/issue41538>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
