[Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows (original) (raw)
Christian Heimes christian at python.org
Mon Oct 22 16:30:23 CEST 2012
- Previous message: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows
- Next message: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 22.10.2012 16:18, schrieb Barry Warsaw:
This is caused by the VMware player installer playing games with $PYTHONHOME to try to point it at its own Python 2 runtime, and trying to call lsbrelease (a Python 3 script on Ubuntu 12.10) while $PYTHONHOME is pointing at the wrong runtime.
I personally think this is a bug in the VMware player installer script.
I think it's a bug in lsb_release, too. It should use the -E option in its shebang:
with "#!/usr/bin/python"
$ PYTHONHOME=/invalid /usr/bin/lsb_release ImportError: No module named site
with "#!/usr/bin/python -E"
$ PYTHONHOME=/invalid /usr/bin/lsb_release LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
- Previous message: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows
- Next message: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]