> On Sun, May 11, 2008 at 12:16 PM, Alan G Isaac <[EMAIL PROTECTED]> wrote:
>> To be specific: I do not recall any place in the NumPy Book
>> where this behavior is promised.
On Sun, 11 May 2008, Robert Kern apparently wrote:
> It's promised in the docstring! """ A matrix is
> a specialized 2
On Sun, May 11, 2008 at 8:09 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Sun, May 11, 2008 at 12:16 PM, Alan G Isaac <[EMAIL PROTECTED]> wrote:
> > To be specific: I do not recall any place in the NumPy Book
> > where this behavior is promised.
>
> It's promised in the docstring!
>
> """ A
On Sun, May 11, 2008 at 12:16 PM, Alan G Isaac <[EMAIL PROTECTED]> wrote:
> To be specific: I do not recall any place in the NumPy Book
> where this behavior is promised.
It's promised in the docstring!
""" A matrix is a specialized 2-d array that retains
it's 2-d nature through operations
""
On Sun, May 11, 2008 at 01:16:44PM -0400, Alan G Isaac wrote:
> That seems like the same thing to me. What I mean is that
> part of the problem is that the handling of scalar indexing
> is being treated as part of the API contract simply because
> it was discoverable behavior.
OK, I didn't und
>> I suspect part of the problem is that "backward
>> compatability" is being interpreted in terms of discoverable
>> behavior, rather than in terms of documented behavior.
On Sun, 11 May 2008, Gael Varoquaux wrote:
> Not at all. It is to be interpreted in terms of "I have
> a few dozens kilol
