> In the cryptography toolkit, the deallocators in the C extensions all > overwrite the object's contents before deallocating it. Is this dodgy > practice? Is it likely or possible that some day PyObject_Del will > need to look at the contents of a non-GC-supporting object before > freeing it? (Encryption or hashing objects are not containers, and > it's highly unlikely they ever will be, so they'll never need to > support GC traversal.) You're safe. PyObject_Del cannot make any assumptions about the contents of the structure -- not even the type pointer or the reference count. Of course you should stay out of the GC header. --Guido van Rossum (home page: http://www.python.org/~guido/)
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