[Numpy-discussion] numpy.sqrt behaving differently on MacOS Lion

Ilan Schnell ischnell at enthought.com
Wed Jul 27 16:33:56 EDT 2011


>     Please don't distribute a different numpy binary for each version of
>     MacOS X.
+1

Maybe I should mention that I just finished testing all Python
packages in EPD under 10.7, and everything (execpt numpy.sqr
for weird complex values such as inf/nan) works fine!
In particular building C and Fortran extensions with the new LLVM
based gcc and importing them into Python (both 32 and 64-bit).
There are two MacOS builds of EPD (one 32-bit and 64-bit), they
are compiled on 10.5 using gcc 4.0.1 and then tested on 10.5, 10.6
and 10.7.

- Ilan


On Wed, Jul 27, 2011 at 3:23 PM, Christopher Barker
<Chris.Barker at noaa.gov> wrote:
> On 7/27/11 12:35 PM, Ralf Gommers wrote:
>>     Please don't distribute a different numpy binary for each version of
>>     MacOS X.
>
> +1 !
>
>> If 10.6-built binaries are going to work without problems on 10.7 - also
>> for scipy - then two versions is enough. I'm not yet confident this will
>> be the case though.
>
> Unless Apple has really broken things (and they usually don't in this
> way), that should be fine.
>
> However, a potential arise when folks want to build their own extensions
> against the python.org (and numpy) binaries.
>
> As I understand it, you can not build extensions to the 32 bit 10.3
> binary on Lion, because Apple has not distributed the 10.4 sdk with
> XCode (nor does it support PPC compilation)
>
> But I think the 10.6+ binaries are fine.
>
> ( wish we had 10.5+ Intel only binaries, as I still need to support
> 10.5, but there are reasons that wasn't done)
>
> No Lion here just yet, so I can't test -- hopefully soon.
>
>> Do the tests for the current 10.6 scipy installer
>> pass on 10.7? And do the 10.3-and-up Python 2.7 and 3.2 binaries work on
>> 10.7? Those are explicitly listed as 10.3-10.6 (not 10.7 ...).
>
> they'll work (the 10.6, not 10.7 is because 10.7 didn't exist yet) --
> with the exception of the above, which is, unfortunately, a common
> numpy/scipy use case.
>
>
> -Chris
>
>
> --
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R            (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
>
> Chris.Barker at noaa.gov
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>



More information about the NumPy-Discussion mailing list