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 christian.heimes
Recipients benjamin.peterson, christian.heimes, georg.brandl, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-07-30.12:25:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343651110.14.0.217882251884.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.

I don't quite understand why Nick thinks that ABI compatibility is a challenge. The structs, typedefs and function definitions aren't modified. The new functions aren't visible because they can be implemented as static functions if PyBuffer_ToContiguous() is moved to memoryview.c. That won't break the ABI eiter.

If we want to keep the function in its old place then we can prefix the new functions with _Py and include them in a private header file. That would export new function.
History
Date User Action Args
2012-07-30 12:25:10christian.heimessetrecipients: + christian.heimes, georg.brandl, ncoghlan, pitrou, vstinner, benjamin.peterson, skrah, meador.inge, python-dev
2012-07-30 12:25:10christian.heimessetmessageid: <1343651110.14.0.217882251884.issue12834@psf.upfronthosting.co.za>
2012-07-30 12:25:09christian.heimeslinkissue12834 messages
2012-07-30 12:25:09christian.heimescreate