Way back on 2012-10-05 23:45:11 GMT in article <nad-7C84D6.16451105102012@news.gmane.org>, I wrote:
In article <nad-B4E67A.00475902102012@news.gmane.org>, Ned Deily <nad@acm.org> wrote:
In article <20121002073135.GA26567@sleipnir.bytereef.org>, Stefan Krah <stefan@bytereef.org> wrote:
Ned Deily <nad@acm.org> wrote:
As discussed here, the python 2.5 binary distributed by Apple on mountain lion is broken. Could someone file an official complaint? I've filed a bug against 10.8 python2.5. The 10.8 versions of Apple's
Forgot the link... http://code.google.com/p/googleappengine/issues/detail?id=7885 On Monday, October 1, 2012, Guido van Rossum wrote: pythons are compile with clang and we did see some sign extension issues with ctypes. The 10.7 version of Apple's python2.5 is compiled with llvm-gcc and handles 2**31 correctly. Yes, this looks like http://bugs.python.org/issue11149 . Ah, right, thanks. I've updated the Apple issue accordingly.
Update: the bug I filed has been closed as a duplicate of #11932488 which apparently at the moment is still open. No other information is available.
FYI, today Apple finally released OS X 10.8.3, the next maintenance release of Mountain Lion, and it does include a recompiled version of Python 2.5.6 that appears to solve the sign-extension problem: 2**31-1 is now 2147483647L. -- Ned Deily, nad@acm.org