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 r.david.murray
Recipients docs@python, ezio.melotti, martin.panter, pitrou, r.david.murray, serhiy.storchaka, skrah
Date 2015-04-02.14:57:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> If a Fortran array was allowed in a bytes-like context without memory copying, the order of the array elements would differ from the order returned by the meoryview.tobytes() method, which essentially is defined to copy them out in C-array or flattend-tolist() order.

I'm still not seeing how this would cause such an object to throw an error if used in a bytes-like context.  I presume by the above that you mean that the results of passing the object directly to a bytes like context differs from the results of calling .tobytes() on it and passing *that* to the bytes like context.  That's not what your suggested documentation change says, though.
Date User Action Args
2015-04-02 14:57:07r.david.murraysetrecipients: + r.david.murray, pitrou, ezio.melotti, skrah, docs@python, martin.panter, serhiy.storchaka
2015-04-02 14:57:07r.david.murraysetmessageid: <>
2015-04-02 14:57:07r.david.murraylinkissue23756 messages
2015-04-02 14:57:07r.david.murraycreate