On Feb 8, 2006, at 9:08 AM, Bill Janssen wrote: >>> In addition, if you have your code running just fine and dandy under >>> Apple's python, then you upgrade to 10.5, chances are that your >>> app will >>> no longer work, as Apple is likely to yank their python out from >>> under >>> you. If it were running with a user-installed Python, chances are it >>> would keep working. >> >> That's something the page should shout to the world about! >> (because I had no idea about this) >> >> "The advantages of not using Apple's versions!" > > You had no idea about it because it's not going to happen. "Apple is > likely to yank their python out from under you"? Come on, this is > absurd. In 10.5, /usr/bin/python is likely to be Python 2.4 instead > of 2.3, but the odds are 9999 to 1 that it will be there, and the > Python community has taken great pains to make sure 2.4 is > backwards-compatible with 2.3.
Yes, you will still be able to run simple scripts that depend on only the standard library and whatever third party stuff Apple consistently ships with Mac OS X. The majority of people use at least some extensions, and any application bundles built with bundlebuilder or py2app are surely toast (unless they depend only on what ships). -bob _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
