On Mon, Mar 26, 2007 at 01:52:28PM -0700, Travis Oliphant wrote:
> I really do want to get 1.0.2 out the door soon. What still needs to be
> fixed before then?
The code in ticket 469 still causes a memory error, so that might be
worth fixing.
Cheers
Stéfan
__
Perry Greenfield wrote:
>Great!
>
>On Mar 26, 2007, at 4:52 PM, Travis Oliphant wrote:
>
>
>
>>I've finally made the changes to fix the scalar coercion model
>>problems
>>in NumPy 1.0.1
>>
>>Now, scalar coercion rules only apply when involved types are of the
>>same basic "kind".
>>
>>
Ac
Great!
On Mar 26, 2007, at 4:52 PM, Travis Oliphant wrote:
> I've finally made the changes to fix the scalar coercion model
> problems
> in NumPy 1.0.1
>
> Now, scalar coercion rules only apply when involved types are of the
> same basic "kind".
[...]
___
I've finally made the changes to fix the scalar coercion model problems
in NumPy 1.0.1
Now, scalar coercion rules only apply when involved types are of the
same basic "kind".
Thus,
array([1,2,3],int8)*10
returns an int8 array
but
array([1,2,3],int8)*10.0
returns a float64 array.
If you wa
