On Oct 02, 2012, at 08:35 PM, Rob Adams wrote: >The problem here is presumably that there's no correct way to set >PYTHONHOME in this case. They need the python2.4 that they ship in the >installer and to point it to their PYTHONHOME. But if from that >environment you ever call any other python program then it will abort >since PYTHONHOME is set incorrectly. What presumably needs to happen is >that python 3 would ignore PYTHONHOME and instread use another variable >PYTHON3HOME (and related) so that there is a correct way to have both >versions of python work.
Well, strictly speaking that's not even correct. They're just getting lucky that setting PYTHONHOME in their script to get their custom Python 2.4 environment doesn't break the system Python 2.7, let alone Python 3.2. IOW, they're already skating on thin ice, but they only broke through in this case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/938869 Title: lsb_release crashed with SIGABRT in Py_FatalError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.2/+bug/938869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
