numpy-discussion

[Numpy-discussion] a**2 not executed as a*a if a.dtype = int32

[Sebastian H. <ha...@ms...>]

Hi,
I submitted this as ticket #230 3weeks ago.
I apparently assigned it to "somebody" - was that a mistake?

Just for refernce, here is the short text again:
 >>> a=N.random.poisson(N.arange(1e6)+1)
 >>> U.timeIt('a**2')
0.59
 >>> U.timeIt('a*a')
0.01
 >>> a.dtype
int32
float64, float32 work OK - giving equal times for both cases. (I tested 
this on Linux 32 bit, Debian sarge)


Am I right that numarray never did this kind of "smart speed up" !?
What are the cases that are speed up like this ? **2, **.5 , ... ??

Thanks,
- Sebastian Haase

Re: [Numpy-discussion] a**2 not executed as a*a if a.dtype = int32

[Robert K. <rob...@gm...>]

Sebastian Haase wrote:
> Hi,
> I submitted this as ticket #230 3weeks ago.
> I apparently assigned it to "somebody" - was that a mistake?

No, that's just the default. When the tickets lists are reliable again, then 
it's also preferred. No, your ticket might not get picked up by anyone because 
of lack of time, but assigning it to someone won't fix that. Let the dev team 
work out the assignment of tickets.

-- 
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

Re: [Numpy-discussion] a**2 not executed as a*a if a.dtype = int32

[Sebastian H. <ha...@ms...>]

Robert Kern wrote:
> Sebastian Haase wrote:
>> Hi,
>> I submitted this as ticket #230 3weeks ago.
>> I apparently assigned it to "somebody" - was that a mistake?
> 
> No, that's just the default. When the tickets lists are reliable again, then 
> it's also preferred. No, your ticket might not get picked up by anyone because 
> of lack of time, but assigning it to someone won't fix that. Let the dev team 
> work out the assignment of tickets.
> 
Thanks for the info -- could this be added on the form ? Like:
""" If you don't have any good reason just leave the fields 'empty' and 
the dev-team will assign proper values soon.
Also don't forget to put yourself in the CC field if you want to track 
changes to the issue you just reported.
"""

  I just think its not obvious for *most* of the choice-fields
what to select ...

Thanks
-Sebastian