ANN: NumPy 1.5.1 release candidate 1
Hi, I am pleased to announce the availability of the first release candidate of NumPy 1.5.1. This is a bug-fix release with no new features compared to 1.5.0. Binaries, sources and release notes can be found at https://sourceforge.net/projects/numpy/files/. A note on the available binaries for OS X: these are known to not work on Intel-based OS X 10.5. We hope to have that problem fixed within a week. On Windows there are still two known test failures: - #1610, in fromfile (under Python 2.x) - #1633, a failing test for ldexp (under Python 2.5 only) Please report any other issues on the Numpy-discussion mailing list. Enjoy, Ralf
On Sun, Oct 17, 2010 at 5:35 AM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
Hi,
I am pleased to announce the availability of the first release candidate of NumPy 1.5.1. This is a bug-fix release with no new features compared to 1.5.0.
Binaries, sources and release notes can be found at https://sourceforge.net/projects/numpy/files/. A note on the available binaries for OS X: these are known to not work on Intel-based OS X 10.5. We hope to have that problem fixed within a week.
On Windows there are still two known test failures: - #1610, in fromfile (under Python 2.x) - #1633, a failing test for ldexp (under Python 2.5 only) Please report any other issues on the Numpy-discussion mailing list.
Test pass for me. osx 10.6 py27 OK (KNOWNFAIL=4, SKIP=2) <nose.result.TextTestResult run=2648 errors=0 failures=0> Vincent
Enjoy, Ralf _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
-- Thanks Vincent Davis 720-301-3003
On Mon, Oct 18, 2010 at 9:55 PM, Vincent Davis <vincent@vincentdavis.net> wrote:
On Sun, Oct 17, 2010 at 5:35 AM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
Hi,
I am pleased to announce the availability of the first release candidate of NumPy 1.5.1. This is a bug-fix release with no new features compared to 1.5.0.
Binaries, sources and release notes can be found at https://sourceforge.net/projects/numpy/files/. A note on the available binaries for OS X: these are known to not work on Intel-based OS X 10.5. We hope to have that problem fixed within a week.
On Windows there are still two known test failures: - #1610, in fromfile (under Python 2.x) - #1633, a failing test for ldexp (under Python 2.5 only) Please report any other issues on the Numpy-discussion mailing list.
Test pass for me. osx 10.6 py27
OK (KNOWNFAIL=4, SKIP=2) <nose.result.TextTestResult run=2648 errors=0 failures=0>
Glad it works for you. But I just reopened the OS X gfortran issue, http://projects.scipy.org/numpy/ticket/1399. RC2 in one week. Two other issues to be fixed by then: http://projects.scipy.org/numpy/ticket/1610 (Pauli has suggested a fix already) http://projects.scipy.org/numpy/ticket/1633 Cheers, Ralf
On Sun, Oct 17, 2010 at 7:35 AM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
Hi,
I am pleased to announce the availability of the first release candidate of NumPy 1.5.1. This is a bug-fix release with no new features compared to 1.5.0. [...] Please report any other issues on the Numpy-discussion mailing list.
Just installed on kubuntu-10.10, python-2.7 and python-3.1.2. Tests look fine for py2.7, but I see datetime errors with py3k: . ====================================================================== ERROR: test_creation (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 10, in test_creation dt1 = np.dtype('M8[750%s]'%unit) TypeError: data type not understood ====================================================================== ERROR: test_creation_overflow (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 62, in test_creation_overflow timesteps = np.array([date], dtype='datetime64[s]')[0].astype(np.int64) TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_as (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 58, in test_divisor_conversion_as self.assertRaises(ValueError, lambda : np.dtype('M8[as/10]')) File "/usr/lib/python3.1/unittest.py", line 589, in assertRaises callableObj(*args, **kwargs) File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 58, in <lambda> self.assertRaises(ValueError, lambda : np.dtype('M8[as/10]')) TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_bday (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 32, in test_divisor_conversion_bday assert np.dtype('M8[B/12]') == np.dtype('M8[2h]') TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_day (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 37, in test_divisor_conversion_day assert np.dtype('M8[D/12]') == np.dtype('M8[2h]') TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_fs (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 54, in test_divisor_conversion_fs assert np.dtype('M8[fs/100]') == np.dtype('M8[10as]') TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_hour (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 42, in test_divisor_conversion_hour assert np.dtype('m8[h/30]') == np.dtype('m8[2m]') TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_minute (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 46, in test_divisor_conversion_minute assert np.dtype('m8[m/30]') == np.dtype('m8[2s]') TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_month (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 21, in test_divisor_conversion_month assert np.dtype('M8[M/2]') == np.dtype('M8[2W]') TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_second (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 50, in test_divisor_conversion_second assert np.dtype('m8[s/100]') == np.dtype('m8[10ms]') TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_week (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 26, in test_divisor_conversion_week assert np.dtype('m8[W/5]') == np.dtype('m8[B]') TypeError: data type not understood ====================================================================== ERROR: test_divisor_conversion_year (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 16, in test_divisor_conversion_year assert np.dtype('M8[Y/4]') == np.dtype('M8[3M]') TypeError: data type not understood ---------------------------------------------------------------------- Ran 3061 tests in 19.197s FAILED (KNOWNFAIL=5, SKIP=4, errors=12) <nose.result.TextTestResult run=3061 errors=12 failures=0>
On Sun, Oct 24, 2010 at 9:22 AM, Darren Dale <dsdale24@gmail.com> wrote:
On Sun, Oct 17, 2010 at 7:35 AM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
Hi,
I am pleased to announce the availability of the first release candidate of NumPy 1.5.1. This is a bug-fix release with no new features compared to 1.5.0. [...] Please report any other issues on the Numpy-discussion mailing list.
Just installed on kubuntu-10.10, python-2.7 and python-3.1.2. Tests look fine for py2.7, but I see datetime errors with py3k:
. ====================================================================== ERROR: test_creation (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 10, in test_creation dt1 = np.dtype('M8[750%s]'%unit) TypeError: data type not understood
====================================================================== ERROR: test_creation_overflow (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 62, in test_creation_overflow timesteps = np.array([date], dtype='datetime64[s]')[0].astype(np.int64) TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_as (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 58, in test_divisor_conversion_as self.assertRaises(ValueError, lambda : np.dtype('M8[as/10]')) File "/usr/lib/python3.1/unittest.py", line 589, in assertRaises callableObj(*args, **kwargs) File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 58, in <lambda> self.assertRaises(ValueError, lambda : np.dtype('M8[as/10]')) TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_bday (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 32, in test_divisor_conversion_bday assert np.dtype('M8[B/12]') == np.dtype('M8[2h]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_day (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 37, in test_divisor_conversion_day assert np.dtype('M8[D/12]') == np.dtype('M8[2h]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_fs (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 54, in test_divisor_conversion_fs assert np.dtype('M8[fs/100]') == np.dtype('M8[10as]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_hour (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 42, in test_divisor_conversion_hour assert np.dtype('m8[h/30]') == np.dtype('m8[2m]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_minute (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 46, in test_divisor_conversion_minute assert np.dtype('m8[m/30]') == np.dtype('m8[2s]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_month (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 21, in test_divisor_conversion_month assert np.dtype('M8[M/2]') == np.dtype('M8[2W]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_second (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 50, in test_divisor_conversion_second assert np.dtype('m8[s/100]') == np.dtype('m8[10ms]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_week (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 26, in test_divisor_conversion_week assert np.dtype('m8[W/5]') == np.dtype('m8[B]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_year (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 16, in test_divisor_conversion_year assert np.dtype('M8[Y/4]') == np.dtype('M8[3M]') TypeError: data type not understood
---------------------------------------------------------------------- Ran 3061 tests in 19.197s
FAILED (KNOWNFAIL=5, SKIP=4, errors=12) <nose.result.TextTestResult run=3061 errors=12 failures=0> ____
You may have left over tests in the installation directory. Can you try deleting it and installing again? Chuck
On Sun, Oct 24, 2010 at 11:29 AM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Sun, Oct 24, 2010 at 9:22 AM, Darren Dale <dsdale24@gmail.com> wrote:
On Sun, Oct 17, 2010 at 7:35 AM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
Hi,
I am pleased to announce the availability of the first release candidate of NumPy 1.5.1. This is a bug-fix release with no new features compared to 1.5.0. [...] Please report any other issues on the Numpy-discussion mailing list.
Just installed on kubuntu-10.10, python-2.7 and python-3.1.2. Tests look fine for py2.7, but I see datetime errors with py3k:
[...]
You may have left over tests in the installation directory. Can you try deleting it and installing again?
You're right. Tests are passing. Darren
hi, this is another instance of a bug caused by the 'no old file handling' problem with distutils/numpy. On Sun, Oct 24, 2010 at 4:29 PM, Charles R Harris <charlesr.harris@gmail.com
wrote:
On Sun, Oct 24, 2010 at 9:22 AM, Darren Dale <dsdale24@gmail.com> wrote:
On Sun, Oct 17, 2010 at 7:35 AM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
Hi,
I am pleased to announce the availability of the first release candidate of NumPy 1.5.1. This is a bug-fix release with no new features compared to 1.5.0. [...] Please report any other issues on the Numpy-discussion mailing list.
Just installed on kubuntu-10.10, python-2.7 and python-3.1.2. Tests look fine for py2.7, but I see datetime errors with py3k:
. ====================================================================== ERROR: test_creation (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 10, in test_creation dt1 = np.dtype('M8[750%s]'%unit) TypeError: data type not understood
====================================================================== ERROR: test_creation_overflow (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 62, in test_creation_overflow timesteps = np.array([date], dtype='datetime64[s]')[0].astype(np.int64) TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_as (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 58, in test_divisor_conversion_as self.assertRaises(ValueError, lambda : np.dtype('M8[as/10]')) File "/usr/lib/python3.1/unittest.py", line 589, in assertRaises callableObj(*args, **kwargs) File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 58, in <lambda> self.assertRaises(ValueError, lambda : np.dtype('M8[as/10]')) TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_bday (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 32, in test_divisor_conversion_bday assert np.dtype('M8[B/12]') == np.dtype('M8[2h]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_day (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 37, in test_divisor_conversion_day assert np.dtype('M8[D/12]') == np.dtype('M8[2h]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_fs (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 54, in test_divisor_conversion_fs assert np.dtype('M8[fs/100]') == np.dtype('M8[10as]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_hour (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 42, in test_divisor_conversion_hour assert np.dtype('m8[h/30]') == np.dtype('m8[2m]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_minute (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 46, in test_divisor_conversion_minute assert np.dtype('m8[m/30]') == np.dtype('m8[2s]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_month (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 21, in test_divisor_conversion_month assert np.dtype('M8[M/2]') == np.dtype('M8[2W]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_second (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 50, in test_divisor_conversion_second assert np.dtype('m8[s/100]') == np.dtype('m8[10ms]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_week (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 26, in test_divisor_conversion_week assert np.dtype('m8[W/5]') == np.dtype('m8[B]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_year (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 16, in test_divisor_conversion_year assert np.dtype('M8[Y/4]') == np.dtype('M8[3M]') TypeError: data type not understood
---------------------------------------------------------------------- Ran 3061 tests in 19.197s
FAILED (KNOWNFAIL=5, SKIP=4, errors=12) <nose.result.TextTestResult run=3061 errors=12 failures=0> ____
You may have left over tests in the installation directory. Can you try deleting it and installing again?
Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Tue, Oct 26, 2010 at 12:35 AM, René Dudfield <renesd@gmail.com> wrote:
hi,
this is another instance of a bug caused by the 'no old file handling' problem with distutils/numpy.
You're talking about the datetime tests below? They don't exist in 1.5.x, that's simply a file left over from an install of the master branch. Cheers, Ralf
On Sun, Oct 24, 2010 at 4:29 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Sun, Oct 24, 2010 at 9:22 AM, Darren Dale <dsdale24@gmail.com> wrote:
On Sun, Oct 17, 2010 at 7:35 AM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
Hi,
I am pleased to announce the availability of the first release candidate of NumPy 1.5.1. This is a bug-fix release with no new features compared to 1.5.0. [...] Please report any other issues on the Numpy-discussion mailing list.
Just installed on kubuntu-10.10, python-2.7 and python-3.1.2. Tests look fine for py2.7, but I see datetime errors with py3k:
. ====================================================================== ERROR: test_creation (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 10, in test_creation dt1 = np.dtype('M8[750%s]'%unit) TypeError: data type not understood
====================================================================== ERROR: test_creation_overflow (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 62, in test_creation_overflow timesteps = np.array([date], dtype='datetime64[s]')[0].astype(np.int64) TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_as (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 58, in test_divisor_conversion_as self.assertRaises(ValueError, lambda : np.dtype('M8[as/10]')) File "/usr/lib/python3.1/unittest.py", line 589, in assertRaises callableObj(*args, **kwargs) File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 58, in <lambda> self.assertRaises(ValueError, lambda : np.dtype('M8[as/10]')) TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_bday (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 32, in test_divisor_conversion_bday assert np.dtype('M8[B/12]') == np.dtype('M8[2h]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_day (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 37, in test_divisor_conversion_day assert np.dtype('M8[D/12]') == np.dtype('M8[2h]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_fs (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 54, in test_divisor_conversion_fs assert np.dtype('M8[fs/100]') == np.dtype('M8[10as]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_hour (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 42, in test_divisor_conversion_hour assert np.dtype('m8[h/30]') == np.dtype('m8[2m]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_minute (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 46, in test_divisor_conversion_minute assert np.dtype('m8[m/30]') == np.dtype('m8[2s]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_month (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 21, in test_divisor_conversion_month assert np.dtype('M8[M/2]') == np.dtype('M8[2W]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_second (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 50, in test_divisor_conversion_second assert np.dtype('m8[s/100]') == np.dtype('m8[10ms]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_week (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 26, in test_divisor_conversion_week assert np.dtype('m8[W/5]') == np.dtype('m8[B]') TypeError: data type not understood
====================================================================== ERROR: test_divisor_conversion_year (test_datetime.TestDateTime) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/darren/.local/lib/python3.1/site-packages/numpy/core/tests/test_datetime.py", line 16, in test_divisor_conversion_year assert np.dtype('M8[Y/4]') == np.dtype('M8[3M]') TypeError: data type not understood
---------------------------------------------------------------------- Ran 3061 tests in 19.197s
FAILED (KNOWNFAIL=5, SKIP=4, errors=12) <nose.result.TextTestResult run=3061 errors=12 failures=0> ____
You may have left over tests in the installation directory. Can you try deleting it and installing again?
Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On 10/26/2010 08:47 AM, Ralf Gommers wrote:
On Tue, Oct 26, 2010 at 12:35 AM, René Dudfield<renesd@gmail.com> wrote:
hi,
this is another instance of a bug caused by the 'no old file handling' problem with distutils/numpy.
You're talking about the datetime tests below? They don't exist in 1.5.x, that's simply a file left over from an install of the master branch.
I think that's what he meant (although the issue has nothing to do with numpy and is solely caused by distutils), cheers, David
Hi, Yeah, that's what I meant. Upgrading numpy over an old install via distutils breaks it. cheers, On Tue, Oct 26, 2010 at 1:54 AM, David <david@silveregg.co.jp> wrote:
On 10/26/2010 08:47 AM, Ralf Gommers wrote:
On Tue, Oct 26, 2010 at 12:35 AM, René Dudfield<renesd@gmail.com> wrote:
hi,
this is another instance of a bug caused by the 'no old file handling' problem with distutils/numpy.
You're talking about the datetime tests below? They don't exist in 1.5.x, that's simply a file left over from an install of the master branch.
I think that's what he meant (although the issue has nothing to do with numpy and is solely caused by distutils),
cheers,
David _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
I found some issues on Mac OS X 10.5 ppc in py2.5.4: See here: http://github.com/friedrichromstedt/numpy/tree/release%2F1.5.1rc1%2Fpy2.5-py... I tested also on 10.6 intel and 10.5 intel, there are no Fs. The Python was freshly installed, only nose & the numpy-py2.5 installer. I'm sorry, I cannot say atm how to get to the installer, we seem to have some port forwarding problem (the build machine and the OS X server in the network seem to be fighting) I discussed with Ralf about what to put into this tree, and I did *not* put binaries. There where binaries in the repo before, but they shouldn't be fetched now, since I removed the branch containing them. One more question: Do I have to install gfortran to do full testing? I see some S. I now say my installer numpy-1.5.1rc1-py2.5-python.org-macosx10.3.dmg, built on 10.5, is fully functional and free to the public. The docs look also good now. Vincent, can you confirm the same for yours? Why do we not ship with the html docs? I find them much more useful than the pdf. I'll continue tomorrow (it's evening here now) with testing in py2.6, py2.7 Vincent's installers if the problem is py2.5 ppc specific. Maybe it's obvious to someone else than me what's going wrong there. The build logs are under release/logs/osx105vmd/. Friedrich
On Wed, Oct 27, 2010 at 1:23 AM, Friedrich Romstedt <friedrichromstedt@gmail.com> wrote:
I found some issues on Mac OS X 10.5 ppc in py2.5.4:
See here:
http://github.com/friedrichromstedt/numpy/tree/release%2F1.5.1rc1%2Fpy2.5-py...
The inf/exp failures should be marked as knownfail, they're not surprising. Not sure about the nextafter and spacing ones (see errors below).
One more question: Do I have to install gfortran to do full testing? I see some S.
If you run the tests with np.test(verbose=2) you can see what's skipped. gfortran is not needed I think, but makes sense to install it anyway - the one recommended athttp://www.scipy.org/Installing_SciPy/Mac_OS_X.
I now say my installer numpy-1.5.1rc1-py2.5-python.org-macosx10.3.dmg, built on 10.5, is fully functional and free to the public. The docs look also good now.
Nice, will check and upload to SF.
Why do we not ship with the html docs? I find them much more useful than the pdf.
Limit download size? Html docs can be read at http://docs.scipy.org/doc/, pdf is for off-line reading, Therefore it makes more sense to include the pdf in the installer. Cheers, Ralf ........................................................................................................Warning: overflow encountered in add Warning: invalid value encountered in subtract Warning: invalid value encountered in subtract Warning: overflow encountered in add Warning: invalid value encountered in subtract Warning: invalid value encountered in subtract ...................................................................................................................................................................................................................................................................................................................................................................K........................................................................................................................................................................................................................................K...K..................Warning: overflow encountered in ldexp .....................................F..F..............................K........F....FFFF.....K........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................S............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. ====================================================================== FAIL: test_umath.test_nextafterl ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/nose/case.py", line 186, in runTest self.test(*self.arg) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/testing/decorators.py", line 215, in knownfailer return f(*args, **kwargs) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/core/tests/test_umath.py", line 1033, in test_nextafterl return _test_nextafter(np.longdouble) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/core/tests/test_umath.py", line 1019, in _test_nextafter assert np.nextafter(one, two) - one == eps AssertionError ====================================================================== FAIL: test_umath.test_spacingl ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/nose/case.py", line 186, in runTest self.test(*self.arg) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/testing/decorators.py", line 215, in knownfailer return f(*args, **kwargs) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/core/tests/test_umath.py", line 1058, in test_spacingl return _test_spacing(np.longdouble) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/core/tests/test_umath.py", line 1042, in _test_spacing assert np.spacing(one) == eps AssertionError ====================================================================== FAIL: test_umath_complex.TestCexp.test_special_values(<ufunc 'exp'>, inf, 0, inf, 0) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/nose/case.py", line 186, in runTest self.test(*self.arg) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/core/tests/test_umath_complex.py", line 579, in check_complex_value assert_equal(f(z1), z2) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/testing/utils.py", line 256, in assert_equal return assert_array_equal(actual, desired, err_msg, verbose) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/testing/utils.py", line 686, in assert_array_equal verbose=verbose, header='Arrays are not equal') File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/testing/utils.py", line 596, in assert_array_compare raise AssertionError(msg) AssertionError: Arrays are not equal (x and y nan location mismatch [ True], False mismatch) x: array([ inf nanj]) y: array((inf+0j)) ====================================================================== FAIL: test_umath_complex.TestCexp.test_special_values(None,) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/nose/case.py", line 186, in runTest self.test(*self.arg) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/core/tests/test_umath_complex.py", line 81, in _check_ninf_inf raise AssertionError(msgform %(z.real, z.imag)) AssertionError: cexp(-inf, inf) is (nan, nan), expected (+-0, +-0) ====================================================================== FAIL: test_umath_complex.TestCexp.test_special_values(None,) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/nose/case.py", line 186, in runTest self.test(*self.arg) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/core/tests/test_umath_complex.py", line 94, in _check_inf_inf raise AssertionError(msgform % (z.real, z.imag)) AssertionError: cexp(inf, inf) is (nan, nan), expected (+-inf, nan) ====================================================================== FAIL: test_umath_complex.TestCexp.test_special_values(None,) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/nose/case.py", line 186, in runTest self.test(*self.arg) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/core/tests/test_umath_complex.py", line 107, in _check_ninf_nan raise AssertionError(msgform % (z.real, z.imag)) AssertionError: cexp(-inf, nan) is (nan, nan), expected (+-0, +-0) ====================================================================== FAIL: test_umath_complex.TestCexp.test_special_values(None,) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/nose/case.py", line 186, in runTest self.test(*self.arg) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/numpy/core/tests/test_umath_complex.py", line 120, in _check_inf_nan raise AssertionError(msgform % (z.real, z.imag)) AssertionError: cexp(-inf, nan) is (nan, nan), expected (+-inf, nan) ---------------------------------------------------------------------- Ran 2992 tests in 50.256s FAILED (KNOWNFAIL=5, SKIP=1, failures=7)
Hi Friedrich, On Wed, Oct 27, 2010 at 10:30 PM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On Wed, Oct 27, 2010 at 1:23 AM, Friedrich Romstedt <friedrichromstedt@gmail.com> wrote:
I found some issues on Mac OS X 10.5 ppc in py2.5.4:
Can you please check if this takes care of all test failures you reported: http://github.com/rgommers/numpy/commit/2ac0be7171f. If not can you please adapt the patch a bit to make it work (should be straightforward)? Thanks, Ralf
Hi Ralf, 2010/11/1 Ralf Gommers <ralf.gommers@googlemail.com>:
On Wed, Oct 27, 2010 at 10:30 PM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On Wed, Oct 27, 2010 at 1:23 AM, Friedrich Romstedt <friedrichromstedt@gmail.com> wrote:
I found some issues on Mac OS X 10.5 ppc in py2.5.4:
Can you please check if this takes care of all test failures you reported: http://github.com/rgommers/numpy/commit/2ac0be7171f.
If not can you please adapt the patch a bit to make it work (should be straightforward)?
Your patch was fine, except for that you spelled 'powerpc' as 'ppc'. This applied also to numpy/core/tests/test_umath_complex.py, see the commits here: http://github.com/friedrichromstedt/numpy/commits/maintenance%2F1.5.1-ppc-kn... I'm not sure if they should be marked as knownfailure instead of being skipped. Looks like legacy to me, as if knownfailureif didn't exist at the time the tests were written. I don't know if there are PowerPC platforms out there which return "ppc" from ``platform.processor()``. Could this apply also to other files? The naming of the branches is of course discussable. We can change this before pulling. Does it apply to 1.5.1 only or also to master? Friedrich
On Tue, Nov 2, 2010 at 7:10 PM, Friedrich Romstedt <friedrichromstedt@gmail.com> wrote:
Hi Ralf,
2010/11/1 Ralf Gommers <ralf.gommers@googlemail.com>:
On Wed, Oct 27, 2010 at 10:30 PM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On Wed, Oct 27, 2010 at 1:23 AM, Friedrich Romstedt <friedrichromstedt@gmail.com> wrote:
I found some issues on Mac OS X 10.5 ppc in py2.5.4:
Can you please check if this takes care of all test failures you reported: http://github.com/rgommers/numpy/commit/2ac0be7171f.
If not can you please adapt the patch a bit to make it work (should be straightforward)?
Your patch was fine, except for that you spelled 'powerpc' as 'ppc'. This applied also to numpy/core/tests/test_umath_complex.py, see the commits here:
Thanks, good to know. I just guessed the 'ppc' part, since the stdlib docs tell me nothing and I couldn't test it.
http://github.com/friedrichromstedt/numpy/commits/maintenance%2F1.5.1-ppc-kn...
I'm not sure if they should be marked as knownfailure instead of being skipped. Looks like legacy to me, as if knownfailureif didn't exist at the time the tests were written.
No, that code is less than a year old. And using knowfail is the correct thing to do here.
I don't know if there are PowerPC platforms out there which return "ppc" from ``platform.processor()``.
Could this apply also to other files?
platform.processor is not used anywhere else, I guess because OS X bugs that don't occur on all machines are mostly 32 vs 64-bit, not i386 vs ppc.
The naming of the branches is of course discussable. We can change this before pulling. Does it apply to 1.5.1 only or also to master?
Branch name doesn't matter, it should be a single fast-forward commit. Applies to master, will update fix and send a pull request for that. Cheers, Ralf
participants (7)
-
Charles R Harris -
Darren Dale -
David -
Friedrich Romstedt -
Ralf Gommers -
René Dudfield -
Vincent Davis