Am 29.07.2011 um 20:23 schrieb Nathaniel Smith:
> Even so, surely this behavior should be consistent between base class
> ndarrays and subclasses? If returning 0d arrays is a good idea, then
> we should do it everywhere. If it's a bad idea, then we shouldn't do
> it at all...?
Very well put. That
Am 29.07.2011 um 17:07 schrieb Mark Wiebe:
> I dug a little bit into the relevant 1.5.x vs 1.6.x code, in the places I
> would most suspect a change, but couldn't find anything obvious.
Thanks for having a look. This strengthens my suspicion that the behavior
change was not intentional.
Have a
On Fri, Jul 29, 2011 at 4:12 AM, Hans Meine
wrote:
>
> /home/hmeine/new_numpy/lib64/python2.6/site-packages/vigra/arraytypes.pyc in
> reshape(self, shape, order)
>587
>588 def reshape(self, shape, order='C'):
> --> 589 res = numpy.ndarray.reshape(self, shape, order)
>590
Hi Martin,
I think it would be more useful if isfinite returned true if *all* elements
were finite. (Opposite of isnan and isinf.)
HTH,
Hans
PS: did not check the complex dtype, hopefully that one's no different.
(The above has been typed using a small on-screen keyboard, which may account
Hi Ben
On Fri, Jul 29, 2011 at 12:57 PM, Benjamin Root wrote:
> I am starting to get very interested in this quaternion concept (and maybe
> how I could use it for mplot3d), but I have never come across it before
> (beyond the typical vector math that I am familiar with). Can anybody
> recommend
On 07/29/2011 11:18 AM, Timo Kluck wrote:
> Dear numpy developers,
>
> The current implementation of numpy.interp(x,xp,fp) comes down to: first
> calculating all the slopes of the linear interpolant (these are
> len(xp)-1), then use a binary search to find where x is in xp (running
> time log(len(x
