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 seberg
Recipients belopolsky, seberg, skrah
Date 2014-09-20.11:43:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1411213422.22337.14.camel@sebastian-t440>
In-reply-to <1411212237.53.0.573609680488.issue22445@psf.upfronthosting.co.za>
Content
An extra dimension is certainly not irrelevant! The strides *are* valid
and numpy currently actually commonly creates such arrays when slicing.
The question is whether or not we want to ignore them for contiguity
checks even if they have no effect on the memory layout.

So there are three options I currently see:

1. Python also generalizes like I would like numpy to end up in the
future (the current patch should do that) and just don't care about such
strides, because the actual memory layout is what matters.
2. We say it is either too dangerous (which may very well be) or you
want to preserve Fortran/C-order information even when it does not
matter to the memory layout.

This leads to this maybe:
2a) we just keep it as it is and live with minor inconsistencies (or
never do the relaxed strides in numpy)
2b) We let these buffers return False on checking for contiguity but
*allow* allow fetching a buffer when C-/F-contiguous is explicitly asked
for when getting the buffer. Which is a weird middle way, but it might
actually be a pretty sane solution (have to think about it).
History
Date User Action Args
2014-09-20 11:43:45sebergsetrecipients: + seberg, belopolsky, skrah
2014-09-20 11:43:45seberglinkissue22445 messages
2014-09-20 11:43:44sebergcreate