[Numpy-discussion] NumPy 1.0 release-candidate 1.0 this weekend

Travis Oliphant oliphant.travis at ieee.org
Wed Sep 13 19:08:43 CDT 2006

Sebastian Haase wrote:
> Hi!
> I would like to hear about three tickets I submitted some time ago:
> Ticket  #230  a**2 not executed as a*a if a.dtype = int32
>   is this easy to fix ?
Fixed.  Now, all arrays with a**2 are executed as a*a (float arrays are 
executed as square(a) (is this needed)?

> Ticket #229   numpy.random.poisson(0) should return 0
>   I hope there is agreement that the edge-case of 0 should/could be handled 
> without raising an exception.  I submitted a patch  (please test first!)
>   any comments on this one.

Fixed.  This seems reasonable to me.

> Ticket #188   dtype should have nicer str representation
>   Is this one now officially dead ? 
>   "<i4"  is not intuitively readable ! '<i4' as repr() is OK 
>    but str() should rather  return   'int32 (little endian)'
It's not necessarily dead, the problem is complexity of implementation 
and more clarity about how all dtypes are supposed to be printed, not 
just this particular example.   A patch would be very helpful here.  If 
desired it could be implemented in _internal.py and called from there in 

But, to get you thinking...  How should the following be printed






More information about the Numpy-discussion mailing list