Hi, On Fri, Apr 26, 2013 at 10:02 AM, Andrew Giessel <[email protected]> wrote: > I like this, thank you Phil. > > From what I can see, the ordering of the returned slices when you use more > than one axis (ie: slices(a, [1,2]), increments the last axis fastest. Does > this makes sense based on the default ordering of, say, nditer()? I know > that C-order (row major) and Fortran order (column major) are two ways of > ordering the returned values- which does this default to? Is there a default > across numpy?
There was a thread on the distinction between index ordering and memory layout starting here: http://www.mail-archive.com/[email protected]/msg40956.html The answer is that C-like index ordering is the default across numpy (last changing fastest), and that, typically (always?) you can change this ordering to Fortran-like (first-fastest) with an 'order' keyword to the function or method. Cheers, Matthew _______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
