[Numpy-discussion] Numeric 24.0

David M. Cooke cookedm at physics.mcmaster.ca
Tue Apr 5 16:13:31 EDT 2005

Travis Oliphant <oliphant at ee.byu.edu> writes:

> I'd like to release a Numeric 24.0  to get the array interface out
> there.   There are also some other bug fixes in Numeric 24.0
> Here is the list so far from Numeric 23.7
> [Greenfield]  Changed so a[0,0] and a[0][0] returns same type when a
> is 2-d of Int16
> [unreported]  Added array interface
> [unreported]  Allow Long Integers to be used in slices
> [1123145]     Handle mu==0.0 appropiately in ranlib/ignpoi.
> [unreported]  Return error info in ranlib instead of printing it to stderr
> [1151892]     dot() would quit python with zero-sized arrays when using
>               dotblas. The BLAS routines *gemv and *gemm need LDA >= 1.
> [unreported]  Fixed empty for Object arrays
> Version 23.8  March 2005
> [Cooke]       Fixed more 64-bit issues (patch 117603)
> [unreported]  Changed arrayfnsmodule back to PyArray_INT where the code
>               typecasts to (int *).  Changed CanCastSafely to check
>               if sizeof(long) == sizeof(int)
> I'll wait a little bit to allow last minute bug fixes to go in, but
> I'd realy like to see this release get out there.  For users of
> Numeric >23.7 try
> Numeric.empty((10,20),'O')  if you want to see an *interesting* bug
> that is fixed in CVS.

Can you hold on? I've got some bugs I'm working on. There's some
64-bit things I'm working (various places that a long is cast to an
int). For instance,

a = Numeric.array((3,))

gives a.shape == (1,) instead of an error. Stuff like this happens in
the new array interface too :-)

I'd suggest, before releasing with a bumped version number to 24.0, we
release a beta version first. Shake out bugs in the array interface,
and potentially allow for some changes if necessary.

|David M. Cooke                      http://arbutus.physics.mcmaster.ca/dmc/
|cookedm at physics.mcmaster.ca

More information about the NumPy-Discussion mailing list