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 martin.panter
Recipients Henning.von.Bargen, benjamin.peterson, docs@python, martin.panter, pitrou, python-dev, r.david.murray, serhiy.storchaka
Date 2016-06-03.07:46:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464940011.11.0.454292635742.issue20699@psf.upfronthosting.co.za>
In-reply-to
Content
Actually this bug report was opened because an implementation that lacked memoryview support was broken by 2.7. The point is to document that (a subset of) memoryview objects may be passed to custom implementations.

Does this need a “changed in 2.7” notice? I am not so familiar with the history of Python 2 or the various buffer APIs to be sure.

Also see <https://bugs.python.org/issue20699#msg266523>, where I discovered array('b') does not work with io.BytesIO.write(). It seems you have to wrap it in buffer() first, presumably because array() does not support the “new” protocol, but buffer() does.
History
Date User Action Args
2016-06-03 07:46:51martin.pantersetrecipients: + martin.panter, pitrou, benjamin.peterson, r.david.murray, docs@python, python-dev, serhiy.storchaka, Henning.von.Bargen
2016-06-03 07:46:51martin.pantersetmessageid: <1464940011.11.0.454292635742.issue20699@psf.upfronthosting.co.za>
2016-06-03 07:46:51martin.panterlinkissue20699 messages
2016-06-03 07:46:50martin.pantercreate