I think we should start a small project for "MacPython Addons", this project will install:
* Hotfix for distutils to ensure that distutils builds univeral binaries (32-bit only at first)
* (possibly) hotfix to ensure that you can install '-fat-' eggs on 10.5 * /Applications/Python-2.5/IDLE.appIn there future we could add other changes, such as a 'python64' command for running python in 64-bit code. IMHO this should be done only when we have patches python.org tree that enable 4-way universal builds on Leopard, otherwise we'd have a real risk of loosing these changes in a future version.
Ronald On 2 Jan, 2008, at 21:33, Bill Janssen wrote:
Even though I've been an open source developer since long before the word existed I find that I'm getting sick and tired of the reinvent-the-world attitude that is far too common in the open source community.If I am new to Python on the Mac and I've played with Apple Python a little, but as soon as I want to install one little add-on module I have to first replace the whole existing Python with something new (and not directly Apple-endorsed) I might just drop out. And at the very least it's mightily inconvenient.Well said, Jack! I think supporting/fixing the Apple-supplied Python should be a goal. I certainly used the Tiger 'Apple' Python for everything, living with its various foibles, and I intend to do the same with Leopard. I can see why cutting edge developers might want to have other versions installed (I've got 2.6 and 3.0 on my Leopard machine, for instance), but all my normal software is developed against /usr/bin/python. Bill
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
