I ended by giving up and grabbing the binary. I'll get 2.5 for Numpy too.
I did grab Xcode 2.5, which has gcc 4.0.1. I didn't feel up to manually doing a complete change to the latest gcc, at least while my needs are being met. Thanks, Nat On Jan 24, 2009, at 9:04 PM, Michael Abshoff wrote: > Robert Kern wrote: >> On Sat, Jan 24, 2009 at 18:31, Nat Wilson <njwilso...@gmail.com> >> wrote: >>> It throws this out. >>> >>> Python 2.6.1 (r261:67515, Jan 24 2009, 16:08:37) >>> [GCC 4.0.0 20041026 (Apple Computer, Inc. build 4061)] on darwin >>> Type "help", "copyright", "credits" or "license" for more >>> information. >>>>>> import os >>>>>> os.urandom(16) >>> '\xe0;n\x8a*\xb4\x08N\x80<\xef\x9b*\x06\x1b\xc4' >>>>>> >> >> Well, looking at the C code for random_seed(), I don't see a way for >> it to return NULL without having an exception set (assuming that the >> Python API calls aren't buggy). Except maybe the assert() call in >> there. When you built your Python, are you sure that -DNDEBUG was >> being used? >> > > Well, the gcc used to compiler Python is rather ancient and that gcc > release by Apple has the reputation to be "buggier than a Florida > swamp > in July" and at least for building Sage it is blacklisted. So I would > suggest updating gcc by using some more recent XCode and trying again. > > Cheers, > > Michael > _______________________________________________ > Numpy-discussion mailing list > Numpy-discussion@scipy.org > http://projects.scipy.org/mailman/listinfo/numpy-discussion _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
