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 skrah
Recipients benjamin.peterson, christian.heimes, georg.brandl, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-07-30.18:13:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343671991.72.0.888857795926.issue12834@psf.upfronthosting.co.za>
In-reply-to
Content
> Right now major parts of the buffer API are broken for non-trivial
> buffer definitions. IMHO a backport of the fix doesn't count as a new
> feature although it needs some new internal functions.

This particular bug fix for PyBuffer_ToContiguous() (which would automatically
fix memoryview.tobytes() in 2.7 and 3.2) is easy to backport.

For non-trivial buffers it's likely though that other problems
will show up in versions 2.7 and 3.2.


Backporting the *complete* rewrite would be relatively easy, too.
But that would change the layout of the MemoryView object etc.

Fixing all of #10181 without the drastic changes would be very time
consuming (if at all possible).
History
Date User Action Args
2012-07-30 18:13:11skrahsetrecipients: + skrah, georg.brandl, ncoghlan, pitrou, vstinner, christian.heimes, benjamin.peterson, meador.inge, python-dev
2012-07-30 18:13:11skrahsetmessageid: <1343671991.72.0.888857795926.issue12834@psf.upfronthosting.co.za>
2012-07-30 18:13:11skrahlinkissue12834 messages
2012-07-30 18:13:10skrahcreate