On 26/10/12 02:57, Mark Lawrence complained that he can't subclass memoryviews:
I'm guessing that I've missed something that's blatantly obvious to
everybody except myself. I can't find a rationale anywhere as to why
I can't subclass memoryviews for my code, so I can't work around
what I perceiv
On 25/10/2012 15:06, Stefan Krah wrote:
Mark Lawrence wrote:
I can't say that this gives me a great deal of confidence. It strikes me
that a lot of code has been written, tested and released without having
anything like a requirement. For example when is any given memoryview
equal to or not equ
Mark Lawrence wrote:
> I can't say that this gives me a great deal of confidence. It strikes me
> that a lot of code has been written, tested and released without having
> anything like a requirement. For example when is any given memoryview
> equal to or not equal to any other memoryview?
A lot
On 24/10/2012 13:19, Nick Coghlan wrote:
(Oops, originally replied only to Mark)
Is a 3x3 array greater or less than a 2x4 array or another 3x3 array?
The contents of a 1D memory view may be sortable, but the "logical
structure" part isn't, and neither is any multi-dimensional view.
I'm surpri
(Oops, originally replied only to Mark)
Is a 3x3 array greater or less than a 2x4 array or another 3x3 array?
The contents of a 1D memory view may be sortable, but the "logical
structure" part isn't, and neither is any multi-dimensional view.
I'm surprised by the lack of inheritance support thou
Original Message
Subject: Python 3.3 can't sort memoryviews as they're unorderable
Date: Sun, 21 Oct 2012 12:24:32 +0100
From: Mark Lawrence
To: python-l...@python.org
Newsgroups: gmane.comp.python.general
http://docs.python.org/dev/whatsnew/3.3.html states "memoryview
compari