Re: [Pythonmac-SIG] newbie Mac switcher trying to set up django on Intel MacBook Pro Tiger

[Ronald Oussoren]

On 3 Jan, 2008, at 15:18, Andrew Jaffe wrote:

Hi All,

I'm not sure whether this is the correct thread/place for this, but is
there any official "best practice" for Python under Leopard?

This is the right thread for that (albeith one with a lame subject).

I.E., should we still be using the MacPython framework build (since I
assume that is more likely to track current python versions than the

Apple build). Is this on the main python or macpython websites somewhere?

Ronald

At the moment Apple's build is a slightly patched [*] version of the current stable release of Python (that is 2.5.1), but with some small issues. AFAIK all issues are related to distutils and are easy to fix. My precious message was a call-to-arms to get a small package out that fixes the issues with Apple's build, which would result in a fully up- to-date python installation including all goodies that Apple ships (PyObjC, wxWidgets, Twisted-Core, ...) and without downloading several huge archives. [*] there is dtrace support in Apple's build and not in the official tree.

Thanks,

Andrew



Ronald Oussoren wrote:

Now that there are several people that want to support Apple's build of

python: how do we go forward from here?

I think we should start a small project for "MacPython Addons", this
project will install:


(32-bit only at first)

* /Applications/Python-2.5/IDLE.app


have patches python.org tree that enable 4-way universal builds on

future version.

Ronald

On 2 Jan, 2008, at 21:33, Bill Janssen wrote:

* Hotfix for distutils to ensure that distutils builds univeral binaries * (possibly) hotfix to ensure that you can install '-fat-' eggs on 10.5 In 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 Leopard, otherwise we'd have a real risk of loosing these changes in a

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.

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.

If I am new to Python on the Mac and I've played with Apple Python a

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

Well said, Jack! I think supporting/fixing the Apple-supplied Python

------------------------------------------------------------------------

_______________________________________________
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

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig