[issue22213] pyvenv style virtual environments unusable in an embedded system

2014-08-23 Thread Graham Dumpleton
Graham Dumpleton added the comment: It is actually very easy for me to work around and I released a new mod_wsgi version today which works. When I get a Python home option, instead of calling Py_SetPythonHome() with it, I append '/bin/python' to it and call Py_SetProgramName() instead. --

[issue22213] pyvenv style virtual environments unusable in an embedded system

2014-08-23 Thread Nick Coghlan
Nick Coghlan added the comment: Some more experiments, comparing an installed vs uninstalled Python. One failure mode is that setting PYTHONHOME just plain breaks running from a source checkout (setting PYTHONHOME to the checkout directory also fails): $ ./python -m venv --without-pip /tmp/iss

[issue22213] pyvenv style virtual environments unusable in an embedded system

2014-08-17 Thread Nick Coghlan
Nick Coghlan added the comment: Graham pointed out that setting PYTHONHOME ends up triggering the same control flow through getpath.c as calling Py_SetPythonHome, so this can be tested just with pyvenv and a suitably configured environment. It may still be a little tricky though, since we norm

[issue22213] pyvenv style virtual environments unusable in an embedded system

2014-08-17 Thread Nick Coghlan
Nick Coghlan added the comment: Yeah, PEP 432 (my proposal to redesign the startup sequence) could just as well be subtitled "getpath.c hurts my brain" :P One tricky part here is going to be figuring out how to test this - perhaps adding a new test option to _testembed and then running it both

[issue22213] pyvenv style virtual environments unusable in an embedded system

2014-08-17 Thread Nick Coghlan
Changes by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue22213] pyvenv style virtual environments unusable in an embedded system

2014-08-17 Thread Graham Dumpleton
New submission from Graham Dumpleton: In am embedded system, as the 'python' executable is itself not run and the Python interpreter is initialised in process explicitly using PyInitialize(), in order to find the location of the Python installation, an elaborate sequence of checks is run as im