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
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 [EMAIL PROTECTED] wrote:
On 4 Dec, 2007, at 22:49, Guido van Rossum wrote:
On OSX
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
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
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:
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!
