On Fri, May 9, 2008 at 11:43 AM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Fri, May 9, 2008 at 1:41 PM, Keith Goodman <[EMAIL PROTECTED]> wrote:
>> That looks good. But at the end of the function I'll have to convert
>> back to a 1d array if the input is 1d
>>
>> np.whence_you_came_from(x)
>>
>>
On Fri, May 9, 2008 at 1:41 PM, Keith Goodman <[EMAIL PROTECTED]> wrote:
> That looks good. But at the end of the function I'll have to convert
> back to a 1d array if the input is 1d
>
> np.whence_you_came_from(x)
>
> I guess there is no way to not test for the shape.
Well, in this case, since yo
On Fri, May 9, 2008 at 11:23 AM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Fri, May 9, 2008 at 12:52 PM, Keith Goodman <[EMAIL PROTECTED]> wrote:
>> The recently proposed changes to the matrix class was the final push I
>> needed to begin slowly porting my package from matrices to arrays. But
>>
On Fri, May 9, 2008 at 12:52 PM, Keith Goodman <[EMAIL PROTECTED]> wrote:
> The recently proposed changes to the matrix class was the final push I
> needed to begin slowly porting my package from matrices to arrays. But
> I'm already stuck in the first stage (all new modules must use
> arrays).
>
>
The recently proposed changes to the matrix class was the final push I
needed to begin slowly porting my package from matrices to arrays. But
I'm already stuck in the first stage (all new modules must use
arrays).
Here's a toy example of iterating over columns of a matrix:
x is a nxm matrix
y is
