[Python-Dev] Mac _OSA extension doesn't build on Leopard

[Ronald Oussoren]

On 5 Dec, 2007, at 17:56, Guido van Rossum wrote:

> Thanks! The sooner the better given that tonight (PST) I plan to do
> the code freeze for the 3.0a2 release, and Anthony is also making
> noises about 2.5.2 again.

I'm working on it right now. I would like a pronouncement on a  
backward incompatible change though:

The _OSA module doesn't compile anymore because it wraps an API that  
was unsupported in 10.4 and was removed in  10.5. I can probably add  
some configury-logic  to detect if the API is still present, but would  
prefer to remove those wrappers completely. That's no problem for 2.6  
and 3.0, but strictly speaking this would introduce a backward  
incompatibility in 2.5.2.

The wrappers are for debugging functionality and unlikely to be used  
by anyone.

BTW. the wrappers for OSADebug* functions are now gone in the trunk  
(as of revision 59369).

Ronald

>
>
> --Guido
>
> On Dec 4, 2007 11:19 PM, Ronald Oussoren <ronaldoussoren at mac.com>  
> wrote:
>>
>> On 4 Dec, 2007, at 22:49, Guido van Rossum wrote:
>>
>>> On OSX 10.5 with Xcode 3.0, whenever I build either the trunk or the
>>> py3k or 25 branches, I get a series of errors when setup.py tries to
>>> build the _OSA module. On OSX 10.4 it builds fine. Can anybody help?
>>> I don't even know what OSA is!
>>
>> I'll try to do a crude fix later this week. The Carbon bindings also
>> wrap some deprecated API's, some of which were dropped in Leopard.
>> We're kind of lucky that _OSA is the only one that no longer  
>> compiles.
>>
>> A correct fix will take some more time, as this will require
>> retargeting the bgen tool to use System headers instead of the OS9  
>> (!)
>> headers that were used to generate the current Carbon bindings.
>>
>> Ronald
>>
>>
>
>
>
> -- 
> --Guido van Rossum (home page: http://www.python.org/~guido/)