As discussed here, the python 2.5 binary distributed by Apple on mountain lion is broken. Could someone file an official complaint? This is really bad...
--Guido
Forgot the link... http://code.google.com/p/googleappengine/issues/detail?id=7885
On Monday, October 1, 2012, Guido van Rossum wrote:
As discussed here, the python 2.5 binary distributed by Apple on mountain lion is broken. Could someone file an official complaint? This is really bad...
--Guido
-- --Guido van Rossum (python.org/~guido)
In article CAP7+vJLYBgPCmKNT5UVzQ9Na3qBdumE9CmJ5PL6yZqR75AyAnw@mail.gmail.com, Guido van Rossum guido@python.org wrote:
Forgot the link... http://code.google.com/p/googleappengine/issues/detail?id=7885
On Monday, October 1, 2012, Guido van Rossum wrote:
As discussed here, the python 2.5 binary distributed by Apple on mountain lion is broken. Could someone file an official complaint? This is really bad...
I've filed a bug against 10.8 python2.5. The 10.8 versions of Apple's 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.
Unfortunately, AFAIK, only the submitter (i.e. me) can see the bug report (problem id 12411585). I'll report back when I hear something.
Ned Deily nad@acm.org wrote:
Forgot the link... http://code.google.com/p/googleappengine/issues/detail?id=7885
On Monday, October 1, 2012, Guido van Rossum wrote:
As discussed here, the python 2.5 binary distributed by Apple on mountain lion is broken. Could someone file an official complaint? This is really bad...
I've filed a bug against 10.8 python2.5. The 10.8 versions of Apple's 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 .
Stefan Krah
In article 20121002073135.GA26567@sleipnir.bytereef.org, Stefan Krah stefan@bytereef.org wrote:
Ned Deily nad@acm.org wrote:
Forgot the link... http://code.google.com/p/googleappengine/issues/detail?id=7885
On Monday, October 1, 2012, Guido van Rossum wrote:
As discussed here, the python 2.5 binary distributed by Apple on mountain lion is broken. Could someone file an official complaint? This is really bad...
I've filed a bug against 10.8 python2.5. The 10.8 versions of Apple's 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.
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:
Forgot the link... http://code.google.com/p/googleappengine/issues/detail?id=7885 On Monday, October 1, 2012, Guido van Rossum 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 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.
On Fri, Oct 5, 2012 at 4:45 PM, Ned Deily nad@acm.org 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:
Forgot the link... http://code.google.com/p/googleappengine/issues/detail?id=7885 On Monday, October 1, 2012, Guido van Rossum 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 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.
Thanks Ned! Is there any way that I could see that bug myself and attach myself to updates? Otherwise, can you keep us here appraised of developments (even if Apple decides not to fix it)?
In article CAP7+vJKeXqYyvfwipOR+7yTdtUs2eDhvybV3tyZb3ZkX6hta5g@mail.gmail.com, Guido van Rossum guido@python.org wrote:
On Fri, Oct 5, 2012 at 4:45 PM, Ned Deily nad@acm.org wrote:
In article nad-B4E67A.00475902102012@news.gmane.org, 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.
Thanks Ned! Is there any way that I could see that bug myself and attach myself to updates? Otherwise, can you keep us here appraised of developments (even if Apple decides not to fix it)?
I don't think there's any way to see any bug other than ones you have submitted yourself. All I can see is that the bug I submitted is closed as a duplicate and now has a Related Problem section that only gives the other incident number and its status (Open). I can't view anything else about that other incident. I don't know if I'll get an email update if its status changes. I'll keep an eye on mine and perhaps ask for a status update if nothing changes in a few weeks.
Thanks, Ned. Do you think it would be worth it to use our contacts at Apple to raise the priority of this embarrassment?
On Saturday, October 6, 2012, Ned Deily wrote:
In article <CAP7+vJKeXqYyvfwipOR+7yTdtUs2eDhvybV3tyZb3ZkX6hta5g@mail.gmail.comjavascript:;
,
Guido van Rossum <guido@python.org javascript:;> wrote:
On Fri, Oct 5, 2012 at 4:45 PM, Ned Deily <nad@acm.org javascript:;>
wrote:
In article <nad-B4E67A.00475902102012@news.gmane.org javascript:;>, 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.
Thanks Ned! Is there any way that I could see that bug myself and attach myself to updates? Otherwise, can you keep us here appraised of developments (even if Apple decides not to fix it)?
I don't think there's any way to see any bug other than ones you have submitted yourself. All I can see is that the bug I submitted is closed as a duplicate and now has a Related Problem section that only gives the other incident number and its status (Open). I can't view anything else about that other incident. I don't know if I'll get an email update if its status changes. I'll keep an eye on mine and perhaps ask for a status update if nothing changes in a few weeks.
-- Ned Deily, nad@acm.org javascript:;
Python-Dev mailing list Python-Dev@python.org javascript:; http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
On Oct 6, 2012, at 20:47 , Guido van Rossum guido@python.org wrote:
On Saturday, October 6, 2012, Ned Deily wrote: In article
CAP7+vJKeXqYyvfwipOR+7yTdtUs2eDhvybV3tyZb3ZkX6hta5g@mail.gmail.com, Guido van Rossum guido@python.org wrote:
On Fri, Oct 5, 2012 at 4:45 PM, Ned Deily nad@acm.org wrote:
In article nad-B4E67A.00475902102012@news.gmane.org, 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.
Thanks Ned! Is there any way that I could see that bug myself and attach myself to updates? Otherwise, can you keep us here appraised of developments (even if Apple decides not to fix it)?
I don't think there's any way to see any bug other than ones you have submitted yourself. All I can see is that the bug I submitted is closed as a duplicate and now has a Related Problem section that only gives the other incident number and its status (Open). I can't view anything else about that other incident. I don't know if I'll get an email update if its status changes. I'll keep an eye on mine and perhaps ask for a status update if nothing changes in a few weeks.
Thanks, Ned. Do you think it would be worth it to use our contacts at Apple to raise the priority of this embarrassment?
It might help if anyone wants to try. On the other hand, Python 2.5 is probably not the highest priority for Apple since they also ship Python 2.6 and 2.7 with 10.8, neither of which have this problem. I'll see if I can get an official status update on mine (#12411585).
-- Ned Deily nad@acm.org -- []
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:
Forgot the link... http://code.google.com/p/googleappengine/issues/detail?id=7885 On Monday, October 1, 2012, Guido van Rossum 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 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.
-
Guido van Rossum -
Ned Deily -
Stefan Krah