[Pythonmac-SIG] ActiveState's OS X Python

[Trent Mick]

> On Jun 7, 2005, at 8:29 AM, Larry Meyn wrote:
> > There's a new kid in town and he doesn't play nice with MacPython (but
> > he does ask first before kicking MacPython aside:)
> >
> > Any thoughts on how this affects the Python development ecosystem for
> > OS X? (.. and right on the heels of the Intel announcements.)
> >
> > http://aspn.activestate.com/ASPN/docs/ActivePython/2.4/
> > installnotes.html#osxpkg

[Sorry, I was a little joining and announcing to this list.]

Larry,
Can you identify any specifics on where ActivePython doesn't play
nicely? The "correct" place for ActivePython to install is the same
place to which MacPython installs (so that things like builds with
"-framework Python" work, etc.). The ActivePython installer *does*
attempt to place nicely by moving MacPython cleanly out of the way. It
leaves the MacPython command-line in a useable state. Specifically
"moving MacPython aside" here means:
    - moving /Library/Frameworks/Python.framework/Versions/2.4
      to /Library/Frameworks/Python.framework/Versions/MacPython2.4
    - prefixing the /usr/local/bin stubs with "mac" so that you have:
        /usr/local/bin/macpython
        /usr/local/bin/macpythonw
        etc.

ActivePython also includes a "pydistro.py" script whose intention is to
eventually simplify managing these kinds of conflicts. Currently
"pydistro.py" has a "macpython_restore" command to restore MacPython to
its original state. Eventually I intend to have a separate download of
pydistro.py available so that the following is easier, but for now, if
you want to get your MacPython back here is what you need to run:

    cd SOME/TEMP/DIR
    cp /Lirary/Receipts/ActivePython-2.4.pkg/Contents/Resources/pydistro.py .
    cp /Lirary/Receipts/ActivePython-2.4.pkg/Contents/Resources/cmdln.py .
    sudo ./pydistro.py activepython_uninstall 2.4
    sudo ./pydistro.py macpython_restore 2.4

I'd love to hear any details you might have on how ActivePython is
misbehaving for you, if at all.

[Bob wrote]
> Since it's installed to the same place, and is the same version of  
> Python, I'd expect the extensions to be interchangeable at least.

Yes. ActivePython should be fully binary compatible with MacPython (of
the same <major>.<minor>). If not, that is a bug.


Sincerely,
Trent

-- 
Trent Mick
TrentM at ActiveState.com