On Feb 5, 2005, at 9:17 PM, has wrote:
Bob Ippolito wrote:
It is not possible to solve this problem without changing the way
Python gets installed (making /usr/bin/python a fork-exec stub or shell
script)
Any reason for not doing that then? Eliminating this wart would be good.
It would break bundlebuilder's --standalone option, probably other things.
How so? The change should only add functionality to /usr/bin/python so that /usr/bin/pythonw is no longer required, allowing the latter to be deprecated and eventually removed. If changing /usr/bin/python itself affects BB, patch BB to reflect the change. (Or just deprecate BB too and tell folk not to use it to build new apps any more. This should be of relatively little inconvenience to users.)
It makes /usr/bin/python depend on another executable at a specific location on the filesystem, bundlebuilder *needs* a local copy of a full Python interpreter, it would also need to be patched.
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). Also, the proposed fixes only fix this issue with a framework Python, not a standard Python, so fixing the GUI frameworks will also make them work with fink and darwinports Python (if they were to build non-X11 GUI frameworks).
-bob
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
