Hi All, NumPy 1.8.0rc1 is up now on sourceforge<http://sourceforge.net/projects/numpy/files/NumPy/1.8.0rc1/>.The binary builds are included except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly. Chuck
Everyone please do actually test this! It is really in your best interest, and I think people don't always realize this. Here's how it works: - If you test it *now*, and it breaks your code that worked with 1.7, and you *tell* us this now, then it's *our* problem and we hold up the release to fix the bug. - If you test it *after* we release, and it breaks your code, then we are sad but you have to work around it (because we can't magically make that release not have happened, your users will be using it anyway), and we put it on the stack with all the other bugs. All of which we care about but it's a large enough stack that it's not going to get any special priority, because, see above about how at this point you'll have had to work around it anyway. -n On Mon, Sep 30, 2013 at 4:17 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
Hi All,
NumPy 1.8.0rc1 is up now on sourceforge .The binary builds are included except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
Chuck
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
On 30 September 2013 17:17, Charles R Harris <charlesr.harris@gmail.com>wrote:
NumPy 1.8.0rc1 is up now on sourceforge<http://sourceforge.net/projects/numpy/files/NumPy/1.8.0rc1/>.The binary builds are included except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
import numpy as np Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.7/site-packages/numpy/__init__.py", line 137, in <module> import add_newdocs File "/usr/lib64/python2.7/site-packages/numpy/add_newdocs.py", line 13, in <module> from numpy.lib import add_newdoc File "/usr/lib64/python2.7/site-packages/numpy/lib/__init__.py", line 4, in <module> from type_check import * File "/usr/lib64/python2.7/site-packages/numpy/lib/type_check.py", line 8, in <module> import numpy.core.numeric as _nx File "/usr/lib64/python2.7/site-packages/numpy/core/__init__.py", line 45, in <module> from numpy.testing import Tester File "/usr/lib64/python2.7/site-packages/numpy/testing/__init__.py", line 10, in <module> import decorators as dec File "/usr/lib64/python2.7/site-packages/numpy/testing/decorators.py",
I installed it with # python setup.py install But something is wrong there: line 19, in <module> from numpy.testing.utils import \ File "/usr/lib64/python2.7/site-packages/numpy/testing/utils.py", line 12, in <module> from .nosetester import import_nose File "/usr/lib64/python2.7/site-packages/numpy/testing/nosetester.py", line 12, in <module> from numpy.compat import basestring ImportError: cannot import name basestring I am using Python27 on Fedora 19. $ gcc --version gcc (GCC) 4.8.1 20130603 (Red Hat 4.8.1-1)
Disregard that, I had not cleaned the previous installation properly. Sorry for the noise. On 1 October 2013 12:11, Daπid <davidmenhur@gmail.com> wrote:
On 30 September 2013 17:17, Charles R Harris <charlesr.harris@gmail.com>wrote:
NumPy 1.8.0rc1 is up now on sourceforge<http://sourceforge.net/projects/numpy/files/NumPy/1.8.0rc1/>.The binary builds are included except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
I installed it with
# python setup.py install
But something is wrong there:
import numpy as np
Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.7/site-packages/numpy/__init__.py", line 137, in <module> import add_newdocs File "/usr/lib64/python2.7/site-packages/numpy/add_newdocs.py", line 13, in <module> from numpy.lib import add_newdoc File "/usr/lib64/python2.7/site-packages/numpy/lib/__init__.py", line 4, in <module> from type_check import * File "/usr/lib64/python2.7/site-packages/numpy/lib/type_check.py", line 8, in <module> import numpy.core.numeric as _nx File "/usr/lib64/python2.7/site-packages/numpy/core/__init__.py", line 45, in <module> from numpy.testing import Tester File "/usr/lib64/python2.7/site-packages/numpy/testing/__init__.py", line 10, in <module> import decorators as dec File "/usr/lib64/python2.7/site-packages/numpy/testing/decorators.py", line 19, in <module> from numpy.testing.utils import \ File "/usr/lib64/python2.7/site-packages/numpy/testing/utils.py", line 12, in <module> from .nosetester import import_nose File "/usr/lib64/python2.7/site-packages/numpy/testing/nosetester.py", line 12, in <module> from numpy.compat import basestring ImportError: cannot import name basestring
I am using Python27 on Fedora 19.
$ gcc --version gcc (GCC) 4.8.1 20130603 (Red Hat 4.8.1-1)
On Mon, Sep 30, 2013 at 09:17:14AM -0600, Charles R Harris wrote:
Hi All,
NumPy 1.8.0rc1 is up now on sourceforge<http://sourceforge.net/projects/numpy/files/NumPy/1.8.0rc1/>.The binary builds are included except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
Chuck
Chuck, The NumPy 1.8.0rc1 release fails to build on Mac OS X 10.6.8 under fink using the build command... /sw/bin/python2.7 setup.py build which fails at... /sw/bin/gfortran -Wall -L/sw/lib build/temp.macosx-10.6-x86_64-2.7/numpy/linalg/lapack_litemodule.o build/temp.macosx-10.6-x86_64-2.7/numpy/linalg/lapack_lite/python_xerbla.o -L/sw/lib -L/sw/lib/gcc4.8/lib/gcc/x86_64-apple-darwin10.8.0/4.8.1 -Lbuild/temp.macosx-10.6-x86_64-2.7 -llapack -lptf77blas -lptcblas -latlas -lgfortran -o build/lib.macosx-10.6-x86_64-2.7/numpy/linalg/lapack_lite.so Undefined symbols for architecture x86_64: "_main", referenced from: start in crt1.10.6.o "_PyOS_snprintf", referenced from: _xerbla_ in python_xerbla.o "_PyGILState_Ensure", referenced from: _xerbla_ in python_xerbla.o "_PyExc_ValueError", referenced from: _xerbla_ in python_xerbla.o etc The full build log is attached. Jack ps The same build approach works fine for the current numpy 1.7.1 release.
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
Charles R Harris <charlesr.harris@gmail.com> writes:
Hi All,
NumPy 1.8.0rc1 is up now on sourceforge .The binary builds are included except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
I have installed 1.0.8rc1 on Python 3.3.2 on Mac OS X Snow Leopard (10.6.8) from the binary installer http://ufpr.dl.sourceforge.net/project/numpy/NumPy/1.8.0rc1/numpy-1.8.0rc1-p... an the test fails with 20 errors. I have tried it also with installing from source but it also gives these erros (I haven't checked if the errors are the same bit for bit, but they were also 20). Here is the output of the test run. -- Piet van Oostrum <piet@vanoostrum.org> WWW: http://pietvanoostrum.com/ PGP key: [8DAE142BE17999C4]
On Wed, Oct 2, 2013 at 2:31 PM, Piet van Oostrum <piet@vanoostrum.org>wrote:
Charles R Harris <charlesr.harris@gmail.com> writes:
Hi All,
NumPy 1.8.0rc1 is up now on sourceforge .The binary builds are included except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
I have installed 1.0.8rc1 on Python 3.3.2 on Mac OS X Snow Leopard (10.6.8) from the binary installer http://ufpr.dl.sourceforge.net/project/numpy/NumPy/1.8.0rc1/numpy-1.8.0rc1-p... the test fails with 20 errors. I have tried it also with installing from source but it also gives these erros (I haven't checked if the errors are the same bit for bit, but they were also 20). Here is the output of the test run.
I'd guess you have the wrong Fortran. IIRC, you have to get it somewhere else than from Apple. Someone else here would know. Chuck
Hi, On Wed, Oct 2, 2013 at 3:42 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Wed, Oct 2, 2013 at 2:31 PM, Piet van Oostrum <piet@vanoostrum.org> wrote:
Charles R Harris <charlesr.harris@gmail.com> writes:
Hi All,
NumPy 1.8.0rc1 is up now on sourceforge .The binary builds are included except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
I have installed 1.0.8rc1 on Python 3.3.2 on Mac OS X Snow Leopard (10.6.8) from the binary installer http://ufpr.dl.sourceforge.net/project/numpy/NumPy/1.8.0rc1/numpy-1.8.0rc1-p... an the test fails with 20 errors. I have tried it also with installing from source but it also gives these erros (I haven't checked if the errors are the same bit for bit, but they were also 20). Here is the output of the test run.
I'd guess you have the wrong Fortran. IIRC, you have to get it somewhere else than from Apple. Someone else here would know.
I don't think he should need Fortran installing from the binary installer - should he? Cheers, Matthew
On Wed, Oct 2, 2013 at 4:48 PM, Matthew Brett <matthew.brett@gmail.com>wrote:
Hi,
On Wed, Oct 2, 2013 at 3:42 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Wed, Oct 2, 2013 at 2:31 PM, Piet van Oostrum <piet@vanoostrum.org> wrote:
Charles R Harris <charlesr.harris@gmail.com> writes:
Hi All,
NumPy 1.8.0rc1 is up now on sourceforge .The binary builds are
included
except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
I have installed 1.0.8rc1 on Python 3.3.2 on Mac OS X Snow Leopard (10.6.8) from the binary installer
http://ufpr.dl.sourceforge.net/project/numpy/NumPy/1.8.0rc1/numpy-1.8.0rc1-p...
an the test fails with 20 errors. I have tried it also with installing from source but it also gives these erros (I haven't checked if the errors are the same bit for bit, but they were also 20). Here is the output of the test run.
I'd guess you have the wrong Fortran. IIRC, you have to get it somewhere else than from Apple. Someone else here would know.
I don't think he should need Fortran installing from the binary installer - should he?
Cheers,
The f2py tests use it. Apparently he has a Fortran, it is just the wrong one. Chuck
On Wed, Oct 2, 2013 at 4:07 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Wed, Oct 2, 2013 at 4:48 PM, Matthew Brett <matthew.brett@gmail.com> wrote:
Hi,
On Wed, Oct 2, 2013 at 3:42 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Wed, Oct 2, 2013 at 2:31 PM, Piet van Oostrum <piet@vanoostrum.org> wrote:
Charles R Harris <charlesr.harris@gmail.com> writes:
Hi All,
NumPy 1.8.0rc1 is up now on sourceforge .The binary builds are included except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
I have installed 1.0.8rc1 on Python 3.3.2 on Mac OS X Snow Leopard (10.6.8) from the binary installer
http://ufpr.dl.sourceforge.net/project/numpy/NumPy/1.8.0rc1/numpy-1.8.0rc1-p... an the test fails with 20 errors. I have tried it also with installing from source but it also gives these erros (I haven't checked if the errors are the same bit for bit, but they were also 20). Here is the output of the test run.
I'd guess you have the wrong Fortran. IIRC, you have to get it somewhere else than from Apple. Someone else here would know.
I don't think he should need Fortran installing from the binary installer - should he?
Cheers,
The f2py tests use it. Apparently he has a Fortran, it is just the wrong one.
Aha - yes - that makes sense, Thanks, Matthew
On Thu, Oct 3, 2013 at 1:07 AM, Charles R Harris <charlesr.harris@gmail.com>wrote:
On Wed, Oct 2, 2013 at 4:48 PM, Matthew Brett <matthew.brett@gmail.com>wrote:
Hi,
On Wed, Oct 2, 2013 at 3:42 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Wed, Oct 2, 2013 at 2:31 PM, Piet van Oostrum <piet@vanoostrum.org> wrote:
Charles R Harris <charlesr.harris@gmail.com> writes:
Hi All,
NumPy 1.8.0rc1 is up now on sourceforge .The binary builds are
except for Python 3.3 on windows, which will arrive later. Many thanks to Ralf for the binaries, and to those who found and fixed the bugs in the last beta. Any remaining bugs are all my fault ;) I hope this will be the last release before final, so please test it thoroughly.
I have installed 1.0.8rc1 on Python 3.3.2 on Mac OS X Snow Leopard (10.6.8) from the binary installer
http://ufpr.dl.sourceforge.net/project/numpy/NumPy/1.8.0rc1/numpy-1.8.0rc1-p...
an the test fails with 20 errors. I have tried it also with installing from source but it also gives these erros (I haven't checked if the errors are the same bit for bit, but they were also 20). Here is the output of
included the test
run.
I'd guess you have the wrong Fortran. IIRC, you have to get it somewhere else than from Apple. Someone else here would know.
I don't think he should need Fortran installing from the binary installer - should he?
Cheers,
The f2py tests use it. Apparently he has a Fortran, it is just the wrong one.
Piet, you should get one of the ones recommended at http://scipy.org/scipylib/building/macosx.html#fortran The last error, test_io.TestSavezLoad, is real though. I can reproduce it, will try to figure it out. Ralf
Ralf Gommers <ralf.gommers@gmail.com> writes:
Piet, you should get one of the ones recommended at http://scipy.org/scipylib/building/macosx.html #fortran
The last error, test_io.TestSavezLoad, is real though. I can reproduce it, will try to figure it out.
I have installed gfortran 4.2.3, which is the one recommended for Snow leopard: bash-3.2$ gfortran -v Using built-in specs. Target: i686-apple-darwin8 Configured with: /Builds/unix/gcc/gcc-4.2/configure --prefix=/usr/local --mandir=/share/man --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --build=i686-apple-darwin8 --host=i686-apple-darwin8 --target=i686-apple-darwin8 --enable-languages=fortran Thread model: posix gcc version 4.2.3 -- Piet van Oostrum <piet@vanoostrum.org> WWW: http://pietvanoostrum.com/ PGP key: [8DAE142BE17999C4]
On Sat, Oct 5, 2013 at 5:34 AM, Piet van Oostrum <piet@vanoostrum.org>wrote:
Ralf Gommers <ralf.gommers@gmail.com> writes:
Piet, you should get one of the ones recommended at http://scipy.org/scipylib/building/macosx.html #fortran
The last error, test_io.TestSavezLoad, is real though. I can reproduce it, will try to figure it out.
I have installed gfortran 4.2.3, which is the one recommended for Snow leopard:
bash-3.2$ gfortran -v Using built-in specs. Target: i686-apple-darwin8 Configured with: /Builds/unix/gcc/gcc-4.2/configure --prefix=/usr/local --mandir=/share/man --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --build=i686-apple-darwin8 --host=i686-apple-darwin8 --target=i686-apple-darwin8 --enable-languages=fortran Thread model: posix gcc version 4.2.3
I can't reproduce it with the exact same OS and Fortran compiler. Looking at the tracebacks a bit more carefully, I see that the compile fails on missing symbols from the Python C API. Did you install Python with the dmg installer from python.org? And can you give the output of "$ locate Python.h"? Ralf
I should have added that yes, I have installed the DMG from python.org. -- Piet van Oostrum <piet@vanoostrum.org> WWW: http://pietvanoostrum.com/ PGP key: [8DAE142BE17999C4]
Ralf Gommers <ralf.gommers@gmail.com> writes:
On Sat, Oct 5, 2013 at 5:34 AM, Piet van Oostrum <piet@vanoostrum.org> wrote:
Ralf Gommers <ralf.gommers@gmail.com> writes:
> Piet, you should get one of the ones recommended at http://scipy.org/scipylib/building/ macosx.html > #fortran > > The last error, test_io.TestSavezLoad, is real though. I can reproduce it, will try to figure it > out. > I have installed gfortran 4.2.3, which is the one recommended for Snow leopard:
bash-3.2$ gfortran -v Using built-in specs. Target: i686-apple-darwin8 Configured with: /Builds/unix/gcc/gcc-4.2/configure --prefix=/usr/local --mandir=/share/man --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --build=i686-apple-darwin8 --host= i686-apple-darwin8 --target=i686-apple-darwin8 --enable-languages=fortran Thread model: posix gcc version 4.2.3
I can't reproduce it with the exact same OS and Fortran compiler. Looking at the tracebacks a bit more carefully, I see that the compile fails on missing symbols from the Python C API. Did you install Python with the dmg installer from python.org? And can you give the output of "$ locate Python.h"?
It does contain (among others) /Library/Frameworks/Python.framework/Versions/3.3/include/python3.3m/Python.h (I am using Python 3.3.2) I have some progress: I reinstalled XCode 3.2.6 after removing the old XCode. And I run the test with the default gcc, which is gcc-4.2 (=version 4.2.1). $ gcc-4.2 -v Using built-in specs. Target: i686-apple-darwin10 Configured with: /var/tmp/gcc/gcc-5666.3~6/src/configure --disable-checking --enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 --with-gxx-include-dir=/include/c++/4.2.1 Thread model: posix gcc version 4.2.1 (Apple Inc. build 5666) (dot 3) On my previous test I used $ export CC=/usr/bin/gcc-4.0 $ export CXX=/usr/bin/g++-4.0 as recommended in http://scipy.org/scipylib/building/macosx.html, but maybe this recommendation is outdated as the Python is compiled with gcc version 4.2.1 Now there is only one error left: ERROR: test_big_arrays (test_io.TestSavezLoad) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/testing/decorators.py", line 146, in skipper_func return f(*args, **kwargs) File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/lib/tests/test_io.py", line 149, in test_big_arrays np.savez(tmp, a=a) File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/lib/npyio.py", line 530, in savez _savez(file, args, kwds, False) File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/lib/npyio.py", line 589, in _savez format.write_array(fid, np.asanyarray(val)) File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/lib/format.py", line 417, in write_array fp.write(array.tostring('C')) OSError: [Errno 22] Invalid argument That's the one you mentioned I think. -- Piet van Oostrum <piet@vanoostrum.org> WWW: http://pietvanoostrum.com/ PGP key: [8DAE142BE17999C4]
On Mon, Oct 7, 2013 at 1:48 PM, Piet van Oostrum <piet@vanoostrum.org>wrote:
Ralf Gommers <ralf.gommers@gmail.com> writes:
On Sat, Oct 5, 2013 at 5:34 AM, Piet van Oostrum <piet@vanoostrum.org> wrote:
Ralf Gommers <ralf.gommers@gmail.com> writes:
> Piet, you should get one of the ones recommended at http://scipy.org/scipylib/building/ macosx.html > #fortran > > The last error, test_io.TestSavezLoad, is real though. I can reproduce it, will try to figure it > out. > I have installed gfortran 4.2.3, which is the one recommended for Snow leopard:
bash-3.2$ gfortran -v Using built-in specs. Target: i686-apple-darwin8 Configured with: /Builds/unix/gcc/gcc-4.2/configure --prefix=/usr/local --mandir=/share/man --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --build=i686-apple-darwin8 --host= i686-apple-darwin8 --target=i686-apple-darwin8 --enable-languages=fortran Thread model: posix gcc version 4.2.3
I can't reproduce it with the exact same OS and Fortran compiler. Looking at the tracebacks a bit more carefully, I see that the compile fails on missing symbols from the Python C API. Did you install Python with the dmg installer from python.org? And can you give the output of "$ locate Python.h"?
It does contain (among others) /Library/Frameworks/Python.framework/Versions/3.3/include/python3.3m/Python.h (I am using Python 3.3.2)
I have some progress: I reinstalled XCode 3.2.6 after removing the old XCode. And I run the test with the default gcc, which is gcc-4.2 (=version 4.2.1).
$ gcc-4.2 -v Using built-in specs. Target: i686-apple-darwin10 Configured with: /var/tmp/gcc/gcc-5666.3~6/src/configure --disable-checking --enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 --with-gxx-include-dir=/include/c++/4.2.1 Thread model: posix gcc version 4.2.1 (Apple Inc. build 5666) (dot 3)
On my previous test I used
$ export CC=/usr/bin/gcc-4.0 $ export CXX=/usr/bin/g++-4.0
as recommended in http://scipy.org/scipylib/building/macosx.html, but maybe this recommendation is outdated as the Python is compiled with gcc version 4.2.1
Ah yes. The recommendation is still valid for Python 2.6, which was the highest Python version available at the time those instructions were written. Python 2.7 from python.org was compiled with gcc 4.2 instead of 4.0.
Now there is only one error left:
ERROR: test_big_arrays (test_io.TestSavezLoad) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/testing/decorators.py", line 146, in skipper_func return f(*args, **kwargs) File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/lib/tests/test_io.py", line 149, in test_big_arrays np.savez(tmp, a=a) File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/lib/npyio.py", line 530, in savez _savez(file, args, kwds, False) File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/lib/npyio.py", line 589, in _savez format.write_array(fid, np.asanyarray(val)) File "/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/numpy/lib/format.py", line 417, in write_array fp.write(array.tostring('C')) OSError: [Errno 22] Invalid argument
That's the one you mentioned I think.
Indeed. That error will be silenced in the final 1.8.0 release. You've got everything working correctly now. Cheers, Ralf
-- Piet van Oostrum <piet@vanoostrum.org> WWW: http://pietvanoostrum.com/ PGP key: [8DAE142BE17999C4]
_______________________________________________ SciPy-User mailing list SciPy-User@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-user
On Python 2.7.5 the test runs without errors, so this might be a Python3 problem (maybe bytes/string confusion?). -- Piet van Oostrum <piet@vanoostrum.org> WWW: http://pietvanoostrum.com/ PGP key: [8DAE142BE17999C4]
participants (7)
-
Charles R Harris -
Daπid -
Jack Howarth -
Matthew Brett -
Nathaniel Smith -
Piet van Oostrum -
Ralf Gommers