> > Failure to call > > this function (if it is != NULL) is a programming error > Not sure I like this. I would prefer to put the burden of "you must provide > a (possibly empty) release function" on the few buffer interface > implementers than the many (ie, potentially any extension author) buffer > interface consumers. The test for whether the release routine is NULL or not (if one is needed at all) surely belongs inside PyObject_ReleaseFixedBuffer. Clients should be required to always call this routine. I say "if one is needed at all" because PyType_Ready could fill it in with a default one if required. Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg@cosc.canterbury.ac.nz +--------------------------------------+
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4