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 lemburg
Recipients benjamin.peterson, eric.araujo, kristjan.jonsson, lemburg
Date 2010-10-27.17:08:29
SpamBayes Score 1.01427e-06
Marked as misclassified No
Message-id <1288199310.98.0.598263439353.issue10211@psf.upfronthosting.co.za>
In-reply-to
Content
The memoryview object was added to simplify porting applications to Python3. If that backport is incomplete in the sense that the memoryview object is not compatible with the standard Python2 object for such memory views, then I'd consider that a bug.

Without compatibility to the buffer objects, there's no way to make other Python2 buffer interface compatible object compatible to memoryviews.

Alternatively, the Python2 memoryview object implementation could also accept objects with the old buffer interface, much like "s*" does.

Note that the patch needs to check the buffer flags - writing to such buffers is not allowed.
History
Date User Action Args
2010-10-27 17:08:31lemburgsetrecipients: + lemburg, kristjan.jonsson, benjamin.peterson, eric.araujo
2010-10-27 17:08:30lemburgsetmessageid: <1288199310.98.0.598263439353.issue10211@psf.upfronthosting.co.za>
2010-10-27 17:08:29lemburglinkissue10211 messages
2010-10-27 17:08:29lemburgcreate