On Feb 5, 2005, at 9:55 PM, has wrote:
Bob Ippolito wrote:
It makes /usr/bin/python depend on another executable at a specific location on the filesystem,
Would it be possible to keep /usr/bin/python as a full-fledged interpreter while adding to it the ability to automatically start a second interpreter at a known location when needed? That should avoid breaking anything that's dependent on there being an interpreter at /usr/bin/python. Or maybe stick the path info in a hidden config file that the interpreter can read when it wants to know its location. I'm not clear on why we need to replace it altogether just to achieve the desired effect.
"when needed" is ambiguous. You don't know you need it until you're well into running Python code. If you knew you needed it in the first place, you'd have run the code with pythonw.
bundlebuilder *needs* a local copy of a full Python interpreter, it would also need to be patched.
How big a job would that be?
Not big, but I'm not going to care.
BTW, what about the sourceforge patches? Would one or both of those solve the problem any better?
No.
Anyway, the best way to do it is to fix the GUI frameworks because that would solve other people's problems too (outside the Python world).
Obviously. Though I think even Jack might struggle at trying to fix Apple itself. :)
It's unlikely that Apple will ever fix this problem for users. I bugged them about it in 2001, and they damn well know the workaround because it's in GLUT (AFTER I had reported it) and Java. We should instead use their private SPI and include the workaround in Tk, wx, SDL, etc.
-bob
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
