Mailman 3 Mac _OSA extension doesn't build on Leopard - Python-Dev - python.org

newer
Does anyone care enough about...

Mac _OSA extension doesn't build on Leopard

older
New Standard Library Module

Guido van Rossum

4 Dec 2007 4 Dec '07

10:49 p.m.

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! -- --Guido van Rossum (home page: http://www.python.org/~guido/)

Reply

Sign in to reply online Use email software

Show replies by date

"Martin v. Löwis"

4 Dec 4 Dec

11:29 p.m.

Can anybody help? I don't even know what OSA is!

I can help with that: It's the Open Scripting Architecture, http://developer.apple.com/documentation/AppleScript/Conceptual/AppleScriptX... (Probably not the kind of help you were asking for :-) Regards, Martin

Reply

Sign in to reply online Use email software

Bill Janssen

5 Dec 5 Dec

4:20 a.m.

I shifted to Leopard a couple of weeks ago. Seems to build and test fine, but I disable all the various poorly documented/maintained Mac modules, so my configure looks like this: ./configure --disable-universalsdk --disable-framework --disable-toolbox-glue I believe OSA is "toolbox glue", so I'll see what happens. Sure enough, looks like the API to the OSA changed with 10.5. Not unreasonable. I'd say, just add "--disable-toobox-glue". Bill

Reply

Sign in to reply online Use email software

Ronald Oussoren

8:19 a.m.

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

Reply

Sign in to reply online Use email software

Guido van Rossum

5:56 p.m.

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. --Guido On Dec 4, 2007 11:19 PM, Ronald Oussoren 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/)

Reply

Sign in to reply online Use email software

Ronald Oussoren

9:08 p.m.

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 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/)

Reply

Sign in to reply online Use email software

Guido van Rossum

9:25 p.m.

How about this: delete them in 2.6 (3.0 will follow after a merge); in 2.5.2, put them inside an #if or #ifdef. Bonus points if you can use a condition that's true on 10.4 and false on 10.5, but always false is okay with me too, as long as there's a comment explaining it. --Guido On Dec 5, 2007 12:08 PM, Ronald Oussoren wrote:

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 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/)

-- --Guido van Rossum (home page: http://www.python.org/~guido/)

Reply

Sign in to reply online Use email software

Ronald Oussoren

9:48 p.m.

On 5 Dec, 2007, at 21:25, Guido van Rossum wrote:

How about this: delete them in 2.6 (3.0 will follow after a merge); in 2.5.2, put them inside an #if or #ifdef. Bonus points if you can use a condition that's true on 10.4 and false on 10.5, but always false is okay with me too, as long as there's a comment explaining it.

There's now a configure test of this in the 2.5 branch (as of revision 59372), the wrappers for OSADebug API's were removed in 2.6 in revision 59369 (earlier tonight) and should be gone in 3.0 after the next merge. Both patches update a generated file, but as it is virtually impossible to regenerate these files at the moment that should be perfectly safe. Ronald

--Guido

On Dec 5, 2007 12:08 PM, Ronald Oussoren wrote:

...
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 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/)

-- --Guido van Rossum (home page: http://www.python.org/~guido/)

Reply

Sign in to reply online Use email software

5985

Age (days ago)

5986

Last active (days ago)

Download

7 comments

4 participants

tags

participants (4)

"Martin v. Löwis"
Bill Janssen
Guido van Rossum
Ronald Oussoren