[Numpy-discussion] Raveling, reshape order keyword unnecessarily confuses index and memory ordering
Chris Barker - NOAA Federal
Tue Apr 2 15:07:57 CDT 2013
On Tue, Apr 2, 2013 at 11:37 AM, <email@example.com> wrote:
> I still don't see why order is not a general concept, whether it
> refers to memory or indexing/iterating.
I agree -- the ordering concept is the same, it's _what_ is being
ordered that's different. So I say we stick with 'C' and 'F' -- numpy
users will need to figure out what it means eventually in any case....
we need some better doc strings and *maybe* renaming a keyword arguemnt or two.
partly I say maybe because the "order" keyword in ravel() actually
mixes the two concepts anyway...
Christopher Barker, Ph.D.
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
More information about the NumPy-Discussion