This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients jcon, kristjan.jonsson, mark.dickinson, ncoghlan, paul.moore, petri.lehtinen, pitrou, pv, rupole, skrah, teoliphant, vstinner
Date 2012-01-28.17:51:36
SpamBayes Score 1.5648028e-06
Marked as misclassified No
Message-id <20120128175136.GA3074@sleipnir.bytereef.org>
In-reply-to <1327771617.8904.3.camel@localhost.localdomain>
Content
Antoine Pitrou <report@bugs.python.org> wrote:
> > Nick Coghlan <report@bugs.python.org> wrote:
> > > Radical suggestion: make it public as collections.simple_ndarray?
> > 
> > Heh, that's a nice one. :)
> 
> Well, the question is: does it have a point? Is this ndarray useful
> outside of any third-party infrastructure such as the APIs offered by
> numpy?

I think it would be mainly educational. It's easier to understand
the whole (multi-dimensional) point of PEP-3118 when there's a
concrete object that you can play with. Of course serious users
would go straight to NumPy.

The other issue is that's it's slightly strange to have a fully
featured memoryview with no object in the stdlib that can utilize
all features (at least the testing side is now complete).

Anyway, right now I don't know myself if I'm for or against it. :)
History
Date User Action Args
2012-01-28 17:51:37skrahsetrecipients: + skrah, teoliphant, paul.moore, mark.dickinson, ncoghlan, rupole, pitrou, kristjan.jonsson, vstinner, pv, jcon, petri.lehtinen
2012-01-28 17:51:37skrahlinkissue10181 messages
2012-01-28 17:51:36skrahcreate