[issue35706] Make it easier to use a venv with an embedded Python interpreter

Steve Dower added the comment: That's not a "see also" - it's just a duplicate :) I'll close this one as the other one has been around longer. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Make pyvenv style virtual environments easier to

[issue35706] Make it easier to use a venv with an embedded Python interpreter

STINNER Victor added the comment: PEP 432 will allow to give with fine control on parameters used to initialize Python. Sadly, I failed to agree with Nick Coghlan and Eric Snow on the API. The current implementation (_PyCoreConfig and _PyMainInterpreterConfig) has some flaw (don't separate

[issue35706] Make it easier to use a venv with an embedded Python interpreter

STINNER Victor added the comment: See also bpo-22213. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35706] Make it easier to use a venv with an embedded Python interpreter

PyScripter added the comment: This issue is related (duplicate) to https://bugs.python.org/issue22213. It appears that there is a workaround but only for Linux using Py_SetProgramName. I wish that there was some similar way for Windows. -- nosy: +ncoghlan, pitrou

[issue35706] Make it easier to use a venv with an embedded Python interpreter

Steve Dower added the comment: > The idea is that python, in the embedding application, should work as in the > python executable. I disagree that this is the idea. Python in the embedding application should work as in the embedding application, not the standalone one. The embedding

[issue35706] Make it easier to use a venv with an embedded Python interpreter

PyScripter added the comment: "Personally, I am 100% against letting an embedded runtime automatically pick up any settings from the environment. You don't know where they came from." Why is that? When the embedding application is using Py_SetPythonHome there is clear intent to use a

[issue35706] Make it easier to use a venv with an embedded Python interpreter

Steve Dower added the comment: Py_Initialize() is not supposed to set it up. If you are embedding Python, you have to be responsible for configuring the paths that it uses - pyvenv.cfg is configuration for Python interactive, not the shared lib (using Windows terminology, it's configuration

[issue35706] Make it easier to use a venv with an embedded Python interpreter

Change by Ned Deily : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___

[issue35706] Make it easier to use a venv with an embedded Python interpreter

PyScripter added the comment: I don't see how pep-0582 is related to embedded python. The solution is to check for the presence of pyvenv.cfg in PYTHONHOME and set up the system.path accordingly. -- ___ Python tracker

[issue35706] Make it easier to use a venv with an embedded Python interpreter

Wolfgang Langner added the comment: I think this pep is related to the issue and could be a solution: https://www.python.org/dev/peps/pep-0582/ -- nosy: +tds333 ___ Python tracker

[issue35706] Make it easier to use a venv with an embedded Python interpreter

PyScripter added the comment: Similar experience. I have found no way to get to use a venv as embedded Python in PyScripter. Tried Py_SetPythonhome, Py_SetPythonName, combinations... Nothing worked. -- nosy: +pyscripter ___ Python tracker

[issue35706] Make it easier to use a venv with an embedded Python interpreter

Change by Dieter Weber : -- title: Making an embedded Python interpreter use a venv is difficult -> Make it easier to use a venv with an embedded Python interpreter ___ Python tracker