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 lgautier
Recipients lgautier, mattip, skrah
Date 2018-12-30.21:57:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Wait. Isn't a `memoryview` memerely a Python object for a buffer inferface, whatever its valid attributes or flags might be ?

The perceived oddness that lead to the addition of the keyword 'shape' was a good initial instinct that something was off, but this is an incomplete workaround .

If the rationale was to follow what `tobytes` is doing, this delegates the justification for excluding non 'C' views it. Then I do not understand the rationale behind `memoryview.tobytes`'s exclusive relationshop to C-contiguous arrays. A memmoryview is a window on a memory region (a Python buffer), and one would expect `tobytes` to just return bytes for it (in whatever bytes/strides) the memoryview is originally in.
Date User Action Args
2018-12-30 21:57:43lgautiersetrecipients: + lgautier, skrah, mattip
2018-12-30 21:57:41lgautiersetmessageid: <>
2018-12-30 21:57:41lgautierlinkissue34778 messages
2018-12-30 21:57:41lgautiercreate