![](https://secure.gravatar.com/avatar/c0da24f75f763b6bac90b519064f30b3.jpg?s=120&d=mm&r=g)
Hello, The source packages and binaries got numpy 1.9.0 beta 2 have just been uploaded to sourceforge. https://sourceforge.net/projects/numpy/files/NumPy/1.9.0b2 1.9.0 will be a new feature release supporting Python 2.6 - 2.7 and 3.2 - 3.4. Unfortunately we have disabled the new __numpy_ufunc__ feature for overriding ufuncs in subclasses for now. There are still some unresolved issues with its behavior regarding python operator precedence and subclasses. If you have a stake in the issue please read Pauli's summary of the remaining issues: http://mail.scipy.org/pipermail/numpy-discussion/2014-July/070737.html When the issues are resolved to everyones satisfaction we hope to enable the feature for 1.10 in its final form. We have restored the indexing edge case that broke matplotlib with numpy 1.9.0 beta 1 but some of the other test failures in other packages are deemed bugs in their code and not reasonable to support in numpy anymore. Most projects have fixed the issues in their latest stable or development versions. Depending on how bad the broken functionality is you may need to update your third party packages when updating numpy to 1.9.0b2. An attempt was made to update the windows binary toolchain to the latest mingw/mingw64 version and an up to date ATLAS version but this turned up a few ugly test failures. Help in resolving these issues is appreciated, no core developer has Windows debugging experience. Please see this issue for details: https://github.com/numpy/numpy/issues/4909 The changelog is mostly the same as in beta1. Please read it carefully there have been many small changes that could affect your code. https://github.com/numpy/numpy/blob/maintenance/1.9.x/doc/release/1.9.0-note... Please also take special note of the future changes section which will apply to the following release 1.10.0 and make sure to check if your applications would be affected by them. Source tarballs, windows installers and release notes can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.9.0b2 Cheers, Julian Taylor
![](https://secure.gravatar.com/avatar/29a8424a5c1ddc5e0e79104965a85011.jpg?s=120&d=mm&r=g)
Hi, I created mingw-w64 builds for testing based on OpenBLAS, see: https://bitbucket.org/carlkl/mingw-w64-for-python/downloads . gists for numpy.test run: win32: https://gist.github.com/carlkl/43182c7c5e0049db7b4e amd64: https://gist.github.com/carlkl/c528505af31ac32720b0 Regards, Carl 2014-07-30 22:20 GMT+02:00 Julian Taylor <jtaylor.debian@googlemail.com>:
![](https://secure.gravatar.com/avatar/b4929294417e9ac44c17967baae75a36.jpg?s=120&d=mm&r=g)
Hi, On Wed, Jul 30, 2014 at 5:12 PM, Carl Kleffner <cmkleffner@gmail.com> wrote:
Thanks all for all the hard work. Here's OSX wheels for testing: http://wheels.scikit-image.org Try with: pip install --pre -f http://wheels.scikit-image.org numpy This should work with Python.org Python on OSX 10.6+, homebrew / macports / system Python for 10.9 [1] Please do send feedback. Cheers, Matthew [1] System Python (/usr/bin/python) will only see your new copy of numpy if you adjust the default path, or test in a virtualenv, because of the system Python sys.path setup
![](https://secure.gravatar.com/avatar/b4929294417e9ac44c17967baae75a36.jpg?s=120&d=mm&r=g)
Hi, On Wed, Jul 30, 2014 at 5:12 PM, Carl Kleffner <cmkleffner@gmail.com> wrote:
I believe the amd64 failure is because Windows doesn't like you trying to open a file that is already open - maybe this will fix it: https://github.com/numpy/numpy/pull/4927 Cheers, Matthew
![](https://secure.gravatar.com/avatar/96dd777e397ab128fedab46af97a3a4a.jpg?s=120&d=mm&r=g)
On Wed, Jul 30, 2014 at 8:42 PM, Matthew Brett <matthew.brett@gmail.com> wrote:
Thanks for getting this out. I just noticed that we are getting a couple of warnings on some platforms. *Python 3.2 debug*; /usr/lib/python3.2/platform.py:381: ResourceWarning: unclosed file <_io.TextIOWrapper name='/etc/lsb-release' mode='rU' encoding='UTF-8'> full_distribution_name=0) *USE_CHROOT=1 ARCH=i386 DIST=trusty PYTHON=3.4* /usr/local/lib/python3.4/dist-packages/numpy/distutils/cpuinfo.py:120: UserWarning: [Errno 2] No such file or directory: '/proc/cpuinfo' warnings.warn(str(e), UserWarning) Not sure about the second one. Chuck
![](https://secure.gravatar.com/avatar/c0da24f75f763b6bac90b519064f30b3.jpg?s=120&d=mm&r=g)
On 31.07.2014 05:20, Charles R Harris wrote:
I just noticed that we are getting a couple of warnings on some platforms.
...
this should harmless, the chroot we use to test 32 bit here does not have the proc filesystem mounted, we could mount it but this distutils feature should not be relevant for travis.
![](https://secure.gravatar.com/avatar/29a8424a5c1ddc5e0e79104965a85011.jpg?s=120&d=mm&r=g)
Hi, I created mingw-w64 builds for testing based on OpenBLAS, see: https://bitbucket.org/carlkl/mingw-w64-for-python/downloads . gists for numpy.test run: win32: https://gist.github.com/carlkl/43182c7c5e0049db7b4e amd64: https://gist.github.com/carlkl/c528505af31ac32720b0 Regards, Carl 2014-07-30 22:20 GMT+02:00 Julian Taylor <jtaylor.debian@googlemail.com>:
![](https://secure.gravatar.com/avatar/b4929294417e9ac44c17967baae75a36.jpg?s=120&d=mm&r=g)
Hi, On Wed, Jul 30, 2014 at 5:12 PM, Carl Kleffner <cmkleffner@gmail.com> wrote:
Thanks all for all the hard work. Here's OSX wheels for testing: http://wheels.scikit-image.org Try with: pip install --pre -f http://wheels.scikit-image.org numpy This should work with Python.org Python on OSX 10.6+, homebrew / macports / system Python for 10.9 [1] Please do send feedback. Cheers, Matthew [1] System Python (/usr/bin/python) will only see your new copy of numpy if you adjust the default path, or test in a virtualenv, because of the system Python sys.path setup
![](https://secure.gravatar.com/avatar/b4929294417e9ac44c17967baae75a36.jpg?s=120&d=mm&r=g)
Hi, On Wed, Jul 30, 2014 at 5:12 PM, Carl Kleffner <cmkleffner@gmail.com> wrote:
I believe the amd64 failure is because Windows doesn't like you trying to open a file that is already open - maybe this will fix it: https://github.com/numpy/numpy/pull/4927 Cheers, Matthew
![](https://secure.gravatar.com/avatar/96dd777e397ab128fedab46af97a3a4a.jpg?s=120&d=mm&r=g)
On Wed, Jul 30, 2014 at 8:42 PM, Matthew Brett <matthew.brett@gmail.com> wrote:
Thanks for getting this out. I just noticed that we are getting a couple of warnings on some platforms. *Python 3.2 debug*; /usr/lib/python3.2/platform.py:381: ResourceWarning: unclosed file <_io.TextIOWrapper name='/etc/lsb-release' mode='rU' encoding='UTF-8'> full_distribution_name=0) *USE_CHROOT=1 ARCH=i386 DIST=trusty PYTHON=3.4* /usr/local/lib/python3.4/dist-packages/numpy/distutils/cpuinfo.py:120: UserWarning: [Errno 2] No such file or directory: '/proc/cpuinfo' warnings.warn(str(e), UserWarning) Not sure about the second one. Chuck
![](https://secure.gravatar.com/avatar/c0da24f75f763b6bac90b519064f30b3.jpg?s=120&d=mm&r=g)
On 31.07.2014 05:20, Charles R Harris wrote:
I just noticed that we are getting a couple of warnings on some platforms.
...
this should harmless, the chroot we use to test 32 bit here does not have the proc filesystem mounted, we could mount it but this distutils feature should not be relevant for travis.
participants (4)
-
Carl Kleffner
-
Charles R Harris
-
Julian Taylor
-
Matthew Brett