On Sun, Sep 8, 2013 at 6:36 PM, Charles R Harris <charlesr.har...@gmail.com>wrote:
> > > > On Sun, Sep 8, 2013 at 3:45 PM, Christoph Gohlke <cgoh...@uci.edu> wrote: > >> On 9/8/2013 12:14 PM, Charles R Harris wrote: >> > Hi all, >> > >> > I'm happy to announce the second beta release of Numpy 1.8.0. This >> > release should solve the Windows problems encountered in the first beta. >> > Many thanks to Christolph Gohlke and Julian Taylor for their hard work >> > in getting those issues settled. >> > >> > It would be good if folks running OS X could try out this release and >> > report any issues on the numpy-dev mailing list. Unfortunately the files >> > still need to be installed from source as dmg files are not avalable at >> > this time. >> > >> > Source tarballs and release notes can be found at >> > https://sourceforge.net/projects/numpy/files/NumPy/1.8.0b2/. The >> Windows >> > and OS X installers will follow when the infrastructure issues are dealt >> > with. >> > >> > Chuck >> > >> >> >> Hello, >> >> I tested numpy 1.8.0b2 with Visual Studio and Intel MKL on Python 2.7 >> and 3.3 for Windows, 32 and 64 bit. There's only a single test failure >> on win-amd64-py3.3, which looks strange since the test expects a >> TypeError to be raised. >> >> ====================================================================== >> ERROR: test_record_no_hash (test_multiarray.TestRecord) >> ---------------------------------------------------------------------- >> Traceback (most recent call last): >> File >> "X:\Python33\lib\site-packages\numpy\core\tests\test_multiarray.py", >> line 2464, in test_record_no_hash >> self.assertRaises(TypeError, hash, a[0]) >> File "X:\Python33\lib\unittest\case.py", line 570, in assertRaises >> return context.handle('assertRaises', callableObj, args, kwargs) >> File "X:\Python33\lib\unittest\case.py", line 135, in handle >> callable_obj(*args, **kwargs) >> File "X:\Python33\lib\unittest\case.py", line 153, in __exit__ >> self.obj_name)) >> TypeError: unhashable type: 'writeable void-scalar' >> >> >> > Hmm, that *is* strange. > > I don't know what to make of the scipy errors at first glance. > > <snip> > > I'm going to guess self.assertRaises tried to hash it again, raising the error again, and we see the second one. The assertRaises from numpy.testing might not have that problem. Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
