[Numpy-discussion] [Announce] Numpy 1.3.0b1

Charles R Harris charlesr.harris@gmail....
Thu Mar 19 10:35:57 CDT 2009


On Thu, Mar 19, 2009 at 9:17 AM, Robert Pyle <rpyle@post.harvard.edu> wrote:

> Hi,
>
> First of all, thanks to everyone for all the hard work.
>
> On Mar 18, 2009, at 10:43 PM, David Cournapeau wrote:
>
> > I am pleased to announce the release of the first beta for numpy
> > 1.3.0. You can find source tarballs and installers for both Mac OS X
>
> I'm on a dual G5 Mac running OS X 10.5.6 and Enthought's EPD python:
>    Python 2.5.2 |EPD Py25 4.1.30101| (r252:60911, Dec 19 2008,
> 15:28:32)
>
> I deleted my old numpy, downloaded the Mac .dmg file and went through
> what claimed to be a successful installation, only to find no numpy.
> I tracked the new version down to /Library/Python/2.5/site-packages, a
> directory that I didn't know existed (site-packages is the only thing
> there).  So I downloaded the source tarball and installed in the usual
> way with no problem into
>
> /Library/Frameworks/Python.framework/Versions/4.1.30101/lib/python2.5/
> site-packages/
>
> So my question is, why did the Mac .mkpg installer put numpy in the
> wrong place?
>
> I'm getting one test failure with 1.3.0b1 ---
>
> FAIL: test_umath.TestComplexFunctions.test_loss_of_precision(<type
> 'numpy.complex256'>,)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/Library/Frameworks/Python.framework/Versions/4.1.30101/lib/
> python2.5/site-packages/nose-0.10.3.0001-py2.5.egg/nose/case.py", line
> 182, in runTest
>     self.test(*self.arg)
>   File "/Library/Frameworks/Python.framework/Versions/4.1.30101/lib/
> python2.5/site-packages/numpy/core/tests/test_umath.py", line 498, in
> check_loss_of_precision
>     check(x_series, 2*eps)
>   File "/Library/Frameworks/Python.framework/Versions/4.1.30101/lib/
> python2.5/site-packages/numpy/core/tests/test_umath.py", line 480, in
> check
>     assert np.all(d < rtol), (np.argmax(d), x[np.argmax(d)], d.max())
> AssertionError: (0, nan, nan)
>

Yes, that test fails on some architectures. What type of cpu do you have? It
would help if you could track down the cause of the nans, see ticket
#1038<http://projects.scipy.org/numpy/ticket/1038>.


Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20090319/59664b79/attachment.html 


More information about the Numpy-discussion mailing list