[Numpy-discussion] ANN: NumPy 1.5.0 beta 2
Christoph Gohlke
cgohlke@uci....
Tue Aug 17 14:38:02 CDT 2010
On 8/17/2010 8:23 AM, Ralf Gommers wrote:
> I am pleased to announce the availability of the second beta of NumPy
> 1.5.0. This will be the first NumPy release to include support for
> Python 3, as well as for Python 2.7.
>
> Please try this beta and report any problems on the NumPy mailing list.
> Especially with Python 3 testing will be very useful. On Linux and OS X
> building from source should be straightforward, for Windows a binary
> installer is provided. There is one important known issue on Windows
> left, in fromfile and tofile (ticket 1583).
>
> Binaries, sources and release notes can be found at
> https://sourceforge.net/projects/numpy/files/
> <https://sourceforge.net/projects/numpy/files/>
>
> Enjoy,
> Ralf
>
NumPy 1.5.0 beta 2 built with msvc9/mkl for Python 2.7 and 3.1 (32 and
64 bit) still reports many (> 200) warnings and three known test
failures/errors. Nothing serious, but it would be nice to clean up
before the final release.
The warnings are of the type "Warning: invalid value encountered in" for
the functions reduce, fmax, fmin, logaddexp, maximum, greater,
less_equal, greater_equal, absolute, and others. I do not see any of
these warnings in the msvc9 builds of numpy 1.4.1.
The following failure appears on 64 bit builds. I guess the test should
be skipped but the platform_skip decorator introduced in changeset 8648
does not take effect because "(np.exp(complex(np.inf, 0)).imag != 0)"
correctly evaluates to False.
======================================================================
FAIL: test_special_values (test_umath_complex.TestClog)
----------------------------------------------------------------------
Traceback (most recent call last):
File "X:\Python27-x64\lib\site-packages\numpy\testing\decorators.py",
line 146, in skipper_func
return f(*args, **kwargs)
File
"X:\Python27-x64\lib\site-packages\numpy\core\tests\test_umath_complex.py",
line 242, in test_special_values
assert_almost_equal(np.log(x), y)
File "X:\Python27-x64\lib\site-packages\numpy\testing\utils.py", line
443, in assert_almost_equal
raise AssertionError(msg)
AssertionError:
Arrays are not almost equal
ACTUAL: array([ nan+2.35619449j])
DESIRED: (inf+2.356194490192345j)
>> raise AssertionError('\nArrays are not almost equal\n ACTUAL: array([ nan+2.35619449j])\n DESIRED: (inf+2.356194490192345j)')
Similar, this failure appears on 32 bit and could be skipped or marked
as known fail:
======================================================================
FAIL: test_special_values (test_umath_complex.TestClog)
----------------------------------------------------------------------
Traceback (most recent call last):
File "X:\Python27\lib\site-packages\numpy\testing\decorators.py",
line 146, in skipper_func
return f(*args, **kwargs)
File
"X:\Python27\lib\site-packages\numpy\core\tests\test_umath_complex.py",
line 162, in test_special_values
self.assertRaises(FloatingPointError, np.log, x)
AssertionError: FloatingPointError not raised
This error can be marked as known for 64 bit builds for Python 2.x (a
patch is attached):
======================================================================
ERROR: Ticket #99
----------------------------------------------------------------------
Traceback (most recent call last):
File "X:\Python27-x64\lib\site-packages\numpy\testing\decorators.py",
line 215, in knownfailer
return f(*args, **kwargs)
File
"X:\Python27-x64\lib\site-packages\numpy\core\tests\test_regression.py",
line 146, in test_intp
np.intp('0x' + 'f'*i_width,16)
TypeError: function takes at most 1 argument (2 given)
The Python 3.1 builds show no additional failures/errors, specifically
not the ones mentioned in ticket 1583.
--
Christoph
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: test_regression.diff
Url: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20100817/b9e16002/attachment.pl
More information about the NumPy-Discussion
mailing list