> Loops using PyDict_Next() to mutate values of existing keys can also > cause __del__ methods to execute (because of decref'ing the old > values), so there are non-gc vulnerabilities there too we haven't > really addressed -- and then even switching to "between opcodes" gc > wouldn't stop the problems unique to gc (since __del__ methods go > back to the eval loop). And it's not just __del__. Lookup operations can invoke arbitrary Python code for the key comparison, which could mutate the dict (or let another thread run that mutates the dict). --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