[Python-Dev] Omit Py_buffer struct from Stable ABI for Python 3.2? (original) (raw)

Antoine Pitrou solipsis at pitrou.net
Wed Jan 5 14:13:23 CET 2011

On Wed, 5 Jan 2011 12:55:55 +0000 Mark Dickinson <dickinsm at gmail.com> wrote:

On Wed, Jan 5, 2011 at 12:31 PM, Nick Coghlan <ncoghlan at gmail.com> wrote: > Currently [1], the implementation and the documentation for PEP 3118's > Pybuffer struct don't line up (there's an extra field in the > implementation that the PEP doesn't mention).

I think there are actually two such fields: smalltable and obj. The need for obj is a little ugly: as far as I can tell, it's meaningless for a 3rd-party object that wants to export buffers---it's only really used by the memoryview object and by internal Python types.

I don't think it's ugly. It's the only way to know which object exported a Py_buffer. Otherwise you have to track the information separately, which is quite a bit uglier (especially when in conjunction with PyArg_ParseTuple and friends).

Regards

Antoine.

More information about the Python-Dev mailing list