Todd Miller <jmiller@stsci.edu> writes: > Point taken. What I'm really proposing is this: Thanks for detailing this proposal. I now agree with your assumption that missing release calls might cause problems; I'd expect that they indeed will cause problems in many applications. The main issue is the interaction with ParseTuple, the 's', 'w', and 't' converters invoke a buffer operation, after which (under your proposal) the object is locked, there is no corresponding release call, and no place to put such a call. So, once you have passed an array to some C function expecting a char*, you cannot extend the array anymore. Regards, Martin
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