Trent, Sorry for the wording, a failed attempt at humor. I just glanced at the announcement and noticed that your installer will move macpython aside, but failed to notice that it adds some symlinks to still access macpython and there is a mechanism to put it back. It's just that having two actively maintained binary framework distros for OS X is a new situation to me (my apologies to MacEnthon, but my impression was that it's still somewhat experimental and Jack has been to busy to maintain his repository lately.)
Actually, another distro is probably a welcome addition as long as the extensions are compatible. I've always used and recommended the ActivePython distro for windows when circumstances require that less friendly OS. I guess my main question was how the entrance of ActiveState would play in the overall development of Python for OS X. More is good, but I hope there will be some productive cooperation with the current prime movers of Python for OS X. (Not me, I'm just a grateful user :) Again, sorry to get things started off on the wrong foot. Your participation is welcomed. Larry On Jun 7, 2005, at 1:30 PM, Trent Mick wrote: >> 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 > [EMAIL PROTECTED] > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig > > Larry Meyn Aerospace Operations Modeling Branch M/S 210-10 NASA Ames Research Center Moffett Field, CA 94035-1000 E-mail: [EMAIL PROTECTED] Phone: (650) 604-5038 Fax: (650) 604-0222 E-Fax: (425) 944-5526 sent via e-mail _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
