On Fri, Mar 2, 2012 at 8:19 PM, Stefan Behnel <stefan...@behnel.de> wrote: > I'm not saying that this is likely to happen, but I could imagine code that > wants to use a different object for the cleanup than itself, possibly for > keeping a certain kind of state when it delivers more than one buffer, or > for remembering what kind of allocation was used, or ...
Supporting that kind of behaviour is what the "internal" field is for. However, given the lack of control, an assert() isn't the appropriate tool here - PyObject_GetBuffer itself should be *checking* the constraint and then reporting an error if the check fails. Otherwise a misbehaving extension module could trivially crash the Python interpreter by returning a bad Py_buffer. Regards, Nick -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
