[Pythonmac-SIG] new Python & wxPython

[Bob Ippolito]

On Apr 4, 2005, at 10:29 PM, Charles Hartman wrote:

> On Apr 4, 2005, at 10:20 PM, Bob Ippolito wrote:
>
>>
>> On Apr 4, 2005, at 10:12 PM, Charles Hartman wrote:
>>
>>> Probably everybody else knows this already, but I'll mention that 
>>> under OS 10.3.8 I'm now happily running Python 2.4.1 with wxPython 
>>> 2.5.4.1. (I had a hard time getting wxPython built -- wouldn't have 
>>> gotten it at all without lots of help from Robin Dunn -- but anyone 
>>> who knew what he or she was doing wouldn't have any trouble.) The 
>>> two *seem* to be playing perfectly happily together.
>>
>> I'd love to see a binary distribution for this.  Building 
>> wxWidgets/wxPython is painful and slow.  I build a lot of stuff, but 
>> wxPython is something I'd rather have someone else deal with..
>>
>> Hopefully the Python 2.4.1 distribution I put out is enough of a 
>> catalyst to get their wheels turning :)
>>
> If I thought I knew enough to do it properly I'd do it happily. I like 
> the combination very much, and I certainly agree it would be nice if 
> it were easier to put together. Of course, Robin D does put together 
> .dmg binaries from time to time; there just isn't one yet for wxPython 
> 2.5.4. I don't know how to do it in a way that allows for the 
> variations (unicode or not, replacing an old installation or not . . . 
> trust me, everybody will be happier if I don't undertake this.

Having a non-unicode build seems pretty stupid to me.  I think the only 
reason it's there is because Jaguar doesn't ship with all the necessary 
libraries, but I don't see why they can't just pull them from elsewhere 
and link them in.  Unlike Windows, Mac OS X doesn't have separate ansi 
and unicode functions for everything.  Some of the crusty old 
deprecated APIs take pascal strings in the system encoding (macroman, 
probably), but those aren't worth using.

-bob