[Pythonmac-SIG] py2app on Tiger

Charles Hartman charles.hartman at conncoll.edu
Thu Mar 17 16:58:58 CET 2005

Thanks, that clarifies it. Since I'm not -- at least in my main current 
project -- compiling any extensions, just using off-the-shelf Python 
2.3 and wxPython, it sounds as though my life shouldn't get *too* much 
more compicated too soon. I'm pretty sure my fairly straightforward 
code isn't using anything in 2.3 that will turn out not to work in 2.4. 
(Famous last words?)

Probably like a lot of people, I don't care much about supporting 
versions of the OS that "nobody" (???) is using. Not only don't I have 
an OS9 version of my application, I don't worry about the absence of a 
10.2 version, because "people" -- which means everyone I know in the 
audience for my weird app -- will have upgraded to 10.3 by now. That 
implies that, from now on, I'll need to keep one (1) bootable partition 
around with the previous x in 10.x, but no more. I'm counting on the 
herd instinct, here.

Charles Hartman

On Mar 17, 2005, at 10:48 AM, Bob Ippolito wrote:

> On Mar 17, 2005, at 10:37, Charles Hartman wrote:
>> On Mar 16, 2005, at 9:39 PM, Bob Ippolito wrote:
>>> You *may* need to compile the Python framework and all of the 
>>> extensions that you use on Mac OS X 10.3 (Panther).  If you *do* 
>>> compile them on Mac OS X 10.3, then they will surely work on Mac OS 
>>> X 10.3.  If you compile them on Mac OS X 10.4 (Tiger), they *might* 
>>> work on Mac OS X 10.3.  It really depends on how they're written, 
>>> what they link to, and how they link to it.  Testing is necessary.
>> Do I have this straight:
>> 1. *Until* I upgrade to Tiger (proably a few months), I can keep 
>> working on 10.3, and what I build (using Apple-distributed framework 
>> 2.3 and wxPython 2.5.3.x or 2.5.4.x when I upgrade that) will work on 
>> *both* 10.3 and 10.4?
> I didn't say that.  I said it would work if you compiled a Python 
> framework.  I said nothing of whether using the Apple-distributed 
> framework would be compatible.  Applications using the stock Python 
> 2.3.x might (let's upgrade that to "will probably") work on both 10.3 
> or 10.4, but there is no guarantee, and it's unlikely to work after 
> that.
>> 2. Once I upgrade, I will need to keep a 10.3 partition around until 
>> I decide to stop supporting 10.3, if ever? Not a cheery prospect, but 
>> I want to make sure I at least understand what it is.
> Compiling extensions on 10.3 is the only way to guarantee they will 
> work on 10.3.  Testing on 10.3 is the only way to know if your app 
> works on 10.3.  The degree to which you need 10.3 depends on how often 
> you need to compile extensions, and how actively you're going to 
> support it by testing.
> -bob

More information about the Pythonmac-SIG mailing list