That's exactly the kind of fix that -- together with a handful of others -- could make this make-over work.
Incorporating the TigerPython24Fix and TigerPython23Compat patches would be another small, huge step. Can the 2.4 installer look at the system and decide which of these is needed? The third piece is a front-end script (part of the installer?? that would be ideal) that checks the user's shell (bash, tcsh, etc) and, perhaps after asking permission, adds the relevant thing to the path. Charles Charles On Feb 9, 2006, at 2:41 PM, Bob Ippolito wrote: > > On Feb 9, 2006, at 10:52 AM, Bill Janssen wrote: > >>> "pythonw" invokes GUI applications, "python" invokes console >>> applications. When installing an extension, I don't type "pythonw >>> setup.py install." >> >> But you could. >> >> No, my conceptual problem is just that you shouldn't need that extra >> "w", and once you start explaining why it's there, there's no good >> place to stop. You start bushwhacking into a thicket of MacPython >> complexity which scares people away. > > If we recommend that the user installs a particular framework build > of Python, we could distribute it such that python and pythonw are > indistinguishable. This issue then disappears. > > -bob > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
