Thanks! More proof that debugging crosses *all* abstractions...
On Wed, Oct 5, 2011 at 4:05 PM, Ned Deily wrote:
> In article
> ,
> Guido van Rossum wrote:
>> Is anyone on this thread interested in other weird Mac bugs? I had a
>> user complaining that on their Mac, with Python 2.5.6 from macpo
In article
,
Guido van Rossum wrote:
> Is anyone on this thread interested in other weird Mac bugs? I had a
> user complaining that on their Mac, with Python 2.5.6 from macports,
> 2**63 was a negative number! That sounds like a compiler bug to me...
>
> http://code.google.com/p/appengine-ndb-e
Is anyone on this thread interested in other weird Mac bugs? I had a
user complaining that on their Mac, with Python 2.5.6 from macports,
2**63 was a negative number! That sounds like a compiler bug to me...
http://code.google.com/p/appengine-ndb-experiment/issues/detail?id=65
(details about the v
In article <74f6adfa-874d-4bac-b304-ce8b12d80...@masklinn.net>,
Xavier Morel wrote:
> On 2011-09-28, at 19:49 , Martin v. Löwis wrote:
> >
> > Thanks for the advise - I didn't expect that Apple ships thhree compilers
> Yeah I can understand that, they're in the middle of the transition but Cla
On 2011-09-28, at 19:49 , Martin v. Löwis wrote:
>
> Thanks for the advise - I didn't expect that Apple ships thhree compilers…
Yeah I can understand that, they're in the middle of the transition but Clang
is not quite there yet so...
___
Python-Dev mai
> Does Clang also fail to compile this? Clang was updated from 1.6 to 2.0 with
> Xcode 4, worth a try.
clang indeed works fine.
> Also, from your version listing it seems to be llvm-gcc (gcc frontend with
> llvm backend I think),
> is there no more straight gcc (with gcc frontend and backend)?
On 2011-09-28, at 13:24 , mar...@v.loewis.de wrote:
> The gcc that Apple ships with the Lion SDK (not sure what Xcode version that
> is)
Xcode 4.1
> I'm not aware of a work-around in the code. My work-around is to use gcc-4.0,
> which is still available on my system from an earlier Xcode installa
