On 7/25/06, Sven Schreiber <[EMAIL PROTECTED]> wrote:
> Travis Oliphant schrieb:
> > Sven Schreiber wrote:
> >>
> > The change was trying to fix up some cases but did break this one. The
> > problem is that figuring out whether or not to transpose the result is a
> > bit tricky. I've obviously st
Travis Oliphant schrieb:
> Sven Schreiber wrote:
>>
> The change was trying to fix up some cases but did break this one. The
> problem is that figuring out whether or not to transpose the result is a
> bit tricky. I've obviously still got it wrong.
>
Ok, this is obviously one of the places
Sven Schreiber wrote:
> Thanks for helping out on matrix stuff, Bill!
>
>
> Hm, I don't know -- if you don't mind I'd like to get a second opinion
> before I mess around there. It's funny though that the changeset has the
> title "fixing up matrix slicing" or something like that...
>
The chan
Thanks for helping out on matrix stuff, Bill!
Bill Baxter schrieb:
> On 7/22/06, Sven Schreiber <[EMAIL PROTECTED]> wrote:
>>
>> Note the array slicing works correct, but the equivalent thing with the
>> matrix does not.
>
> Looks like it happened in rev 2698 of defmatrix.py, matrix.__getitem__
Howdy,
On 7/22/06, Sven Schreiber <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Summary: Slicing seems to be broken with matrices now.
>
> ...
> Example:
>
> >>> import numpy as n
> >>> n.__version__
> '1.0b1'
> >>> import numpy.matlib as m
> >>> a = n.zeros((2,3))
> >>> b = m.zeros((2,3))
> >>> a[:1,:].sh
Hi,
Summary: Slicing seems to be broken with matrices now.
I eagerly installed the new beta, but soon stumbled over this
bug. I hope I'm missing something, but afaics that behavior used to be
different (and correct) before in 0.9.8. Don't know exactly when this
changed, though. I did a fresh inst
