On 14 January 2016 at 15:42, Benjamin Peterson <benjamin at python.org> wrote: > This is a "well-known" issue. Parts of the interpreter (and especially, > extension modules) cheerfully stash objects in global variables with no > way to clean them up. Fixing this is a large project, which probably > involves implementing PEP 489. The actual multi-phase extension module import system from 489 was implemented for 3.5, but indeed, the modules with stashed global state haven't been converted yet. I didn't think we loaded any of those by default, though... Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
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