This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Allow customizing python interpreter in venv.EnvBuilder
Type: enhancement Stage: patch review
Components: Library (Lib) Versions: Python 3.10
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: abbec, vinay.sajip
Priority: normal Keywords: patch

Created on 2020-08-13 08:31 by abbec, last changed 2022-04-11 14:59 by admin.

Pull Requests
URL Status Linked Edit
PR 21854 open abbec, 2020-08-13 11:35
Messages (1)
msg375293 - (view) Author: Albert Cervin (abbec) * Date: 2020-08-13 08:31
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.
Date User Action Args
2022-04-11 14:59:34adminsetgithub: 85710
2020-08-13 11:35:17abbecsetkeywords: + patch
stage: patch review
pull_requests: + pull_request20981
2020-08-13 11:09:31xtreaksetnosy: + vinay.sajip

versions: - Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9
2020-08-13 08:31:20abbeccreate