[Numpy-discussion] numpy release
Hi Jarrod, any news with the 1.0.5? If you have same prerelease, I'd like to test it. Debian has just moved from python2.4 to python2.5 yesterday, so I'd like to test numpy in advance, I am sure there will be some issues to fix. Ondrej ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Win32 installer: please test it
Tested fine on my old Classic Athlon 500 (no SSE) under Win98. It correctly reported installing the non-SSE version when I clicked on the details button on the last page of the install wizard. Whereas previously numpy.test() would bring up an illegal operation dialog box, now all tests pass. Nice!. Gary R. N.test() Numpy is installed in C:\PYTHON25\lib\site-packages\numpy Numpy version 1.0.5.dev5008 Python version 2.5.2a0 (release25-maint:59715M, Jan 3 2008, 22:45:43) [MSC v.13 10 32 bit (Intel)] Found 10/10 tests for numpy.core.defmatrix Found 3/3 tests for numpy.core.memmap Found 266/266 tests for numpy.core.multiarray Found 69/69 tests for numpy.core.numeric Found 31/31 tests for numpy.core.numerictypes Found 12/12 tests for numpy.core.records Found 7/7 tests for numpy.core.scalarmath Found 16/16 tests for numpy.core.umath Found 5/5 tests for numpy.ctypeslib Found 5/5 tests for numpy.distutils.misc_util Found 2/2 tests for numpy.fft.fftpack Found 3/3 tests for numpy.fft.helper Found 20/20 tests for numpy.lib._datasource Found 10/10 tests for numpy.lib.arraysetops Found 1/1 tests for numpy.lib.financial Found 0/0 tests for numpy.lib.format Found 48/48 tests for numpy.lib.function_base Found 5/5 tests for numpy.lib.getlimits Found 4/4 tests for numpy.lib.index_tricks Found 7/7 tests for numpy.lib.io Found 4/4 tests for numpy.lib.polynomial Found 49/49 tests for numpy.lib.shape_base Found 15/15 tests for numpy.lib.twodim_base Found 43/43 tests for numpy.lib.type_check Found 1/1 tests for numpy.lib.ufunclike Found 59/59 tests for numpy.linalg Found 92/92 tests for numpy.ma.core Found 14/14 tests for numpy.ma.extras Found 7/7 tests for numpy.random Found 0/0 tests for numpy.testing.utils Found 0/0 tests for __main__ ... -- Ran 887 tests in 7.580s OK unittest._TextTestResult run=887 errors=0 failures=0 Jarrod Millman wrote: Hello, David Cournapeau has prepared a new win32 installer, which is aimed at solving the recurring problem of non working atlas on different sets of CPU. This installer simply checks which cpu you have, and installs the appropriate numpy accordingly (without atlas if your cpu is not supported). Windows users, please test the installer, and report ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Win32 installer: please test it
Everything installed without problem on Intel Pentium M on my notebook
recognized as SSE2 capable.
Installer found Python 2.5. immediately, which I just installed and
all my windows environment settings are still setup for python 2.4
Thanks,
Josef
numpy.test()
Numpy is installed in C:\Programs\Python25\lib\site-packages\numpy
Numpy version 1.0.5.dev5008
Python version 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310
32 bit (Intel)]
Found 10/10 tests for numpy.core.defmatrix
Found
...
--
Ran 887 tests in 5.922s
OK
unittest._TextTestResult run=887 errors=0 failures=0
numpy.show_config()
atlas_threads_info:
NOT AVAILABLE
blas_opt_info:
libraries = ['f77blas', 'cblas', 'atlas']
library_dirs = ['C:\\local\\lib\\sse2']
define_macros = [('NO_ATLAS_INFO', 2)]
language = c
atlas_blas_threads_info:
NOT AVAILABLE
lapack_opt_info:
libraries = ['lapack', 'f77blas', 'cblas', 'atlas']
library_dirs = ['C:\\local\\lib\\sse2']
define_macros = [('NO_ATLAS_INFO', 2)]
language = f77
atlas_info:
libraries = ['lapack', 'f77blas', 'cblas', 'atlas']
library_dirs = ['C:\\local\\lib\\sse2']
language = f77
lapack_mkl_info:
NOT AVAILABLE
blas_mkl_info:
NOT AVAILABLE
atlas_blas_info:
libraries = ['f77blas', 'cblas', 'atlas']
library_dirs = ['C:\\local\\lib\\sse2']
language = c
mkl_info:
NOT AVAILABLE
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ones with non-native dtype byteorder
This (on little-endian machine) surprised me: In [23]:np.ones((1,), dtype='i2') Out[23]:array([1], dtype=int16) In [24]:np.ones((1,), dtype='i2') Out[24]:array([256], dtype=int16) I expected the value to be [1] in either case. Am I wrong? The docstring gives no hint that this is how the dtype argument will be interpreted. In [27]:np.__version__ Out[27]:'1.0.5.dev4958' Eric ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] ones with non-native dtype byteorder
On Mon, Apr 14, 2008 at 1:59 PM, Eric Firing [EMAIL PROTECTED] wrote: This (on little-endian machine) surprised me: In [23]:np.ones((1,), dtype='i2') Out[23]:array([1], dtype=int16) In [24]:np.ones((1,), dtype='i2') Out[24]:array([256], dtype=int16) I expected the value to be [1] in either case. Am I wrong? You are correct. It is a bug in the @[EMAIL PROTECTED]() template in arraytypes.inc.src; it does not take endianness into consideration. I mentioned this to Travis, and he might have time to hop on this, but if anyone else can fix it faster, please go for it. -- Robert Kern I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth. -- Umberto Eco ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Win32 installer: please test it (Bill Baxter)
Neil Crighton wrote: The Win32 installer works on my Vista machine. There is one failed test, but I think that's just because it tries to write somewhere it doesn't have permission - I installed Python in /Program Files/Python25/, and you need to be an administrator to write to Program Files/. Here's the error message: ERROR: test_ValidHTTP (numpy.lib.tests.test__datasource.TestDataSourceOpen) -- Traceback (most recent call last): File C:\Program Files\Python25\lib\site-packages\numpy\lib\tests\test__datasource.py, line 79, in test_ValidHTTP assert self.ds.open(valid_httpurl()) File C:\Program Files\Python25\lib\site-packages\numpy\lib\_datasource.py, line 366, in open found = self._findfile(path) File C:\Program Files\Python25\lib\site-packages\numpy\lib\_datasource.py, line 243, in _findfile name = self._cache(name) File C:\Program Files\Python25\lib\site-packages\numpy\lib\_datasource.py, line 203, in _cache file(upath, 'w').write(openedurl.read()) IOError: [Errno 13] Permission denied: '/index.html' -- Ran 887 tests in 4.914s Yes, I noticed that too. I opened a bug, but this has nothing to do with this installer, this would have happened anyway. David ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Release of NumPy
After the SciPy sprints some useful discussions took place that helped us all realize that we have made enough changes to the code base that we will need to call any release from the trunk 1.1 I don't think that is a big problem. However, there have also been a lot of substantial bug fixes that really deserve to be applied against 1.0.4 and released as 1.0.5 So, the question is. Do we have enough energy in the community to release the current trunk as 1.1 as well as release 1.0.5 which does not contain any of the code/api changes, but just the bug fixes? The answer will be yes if somebody volunteers to back-port just the bug-fixes to 1.0.4.I would really like there to be a bug-fix 1.0.5 release if at all possible. Best regards, -Travis ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Release of NumPy
On Mon, Apr 14, 2008 at 9:59 PM, Travis E. Oliphant [EMAIL PROTECTED] wrote: So, the question is. Do we have enough energy in the community to release the current trunk as 1.1 as well as release 1.0.5 which does not contain any of the code/api changes, but just the bug fixes? The answer will be yes if somebody volunteers to back-port just the bug-fixes to 1.0.4.I would really like there to be a bug-fix 1.0.5 release if at all possible. Personally, I would rather see everyone's effort focused on 1.1 and the 1.2 (previously referred to as 1.1). But if anyone is interested in backporting some of the bug-fixes, I will help coordinate a 1.0.5 release. For now, I hope to keep everyone focused on the trunk, which will become 1.1.0 very soon. I will send out an email fairly soon listing the last things that need to be done before releasing 1.1.0. Basically, I would like to have some testing of the new Windows and Mac binaries. David C. has all ready sent out an email asking for help testing the new Window's binaries. Chris Burns or I will be sending out an email asking for help testing the new Universal Mac binaries within the next day. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Release of NumPy
On Mon, Apr 14, 2008 at 10:59 PM, Travis E. Oliphant [EMAIL PROTECTED] wrote: After the SciPy sprints some useful discussions took place that helped us all realize that we have made enough changes to the code base that we will need to call any release from the trunk 1.1 I don't think that is a big problem. However, there have also been a lot of substantial bug fixes that really deserve to be applied against 1.0.4 and released as 1.0.5 So, the question is. Do we have enough energy in the community to release the current trunk as 1.1 as well as release 1.0.5 which does not contain any of the code/api changes, but just the bug fixes? The answer will be yes if somebody volunteers to back-port just the bug-fixes to 1.0.4.I would really like there to be a bug-fix 1.0.5 release if at all possible. I think we have a long way to go to get to 1.1. What API changes have we made that are so great that we can't release 1.0.5? The only area where I have seen real problems is in masked arrays. My preference would be to release the trunk as 1.0.5, and if not, simply deprecate 1.0.4 and move to 1.1. I don't think it's worth the time and effort to backport anything. Chuck ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Release of NumPy
On Mon, Apr 14, 2008 at 10:38 PM, Charles R Harris [EMAIL PROTECTED] wrote: Let's not rush 1.1, then. I think with another week or two we should be able to settle most of the outstanding bugs and it would be good to do so before getting caught up in planning 1.2. +1. I think that we are so close to closing every reported bug that spending another week or two would be wise. I also want to have very stable and easy-to-use binaries for both Windows and Mac for this release, which we are very close to doing. Chris has all ready made MacOS X binaries; he is just cleaning up a few things before asking for more testing. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Release of NumPy
On Mon, 14 Apr 2008, Charles R Harris apparently wrote: Let's not rush 1.1, then. Will matrix behavior change in 1.1, as discussed from time to time? Perhaps it just takes a very small change in __getitem__: URL:http://www.mail-archive.com/numpy-discussion@scipy.org/msg07363.html Cheers, Alan Isaac ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
