Le 21/10/2015 17:32, Raymond Hettinger a écrit : > > Thanks for hunting this down. I had seen the automated reference leak posts > but didn't suspect that a pure python class would have caused the leak. Yes, it's a bit baffling at first. > I'm re-opening https://mail.python.org/pipermail/python-dev/2015-October/141993.html > and will take a look at it this weekend. If I don't see an obvious fix, I'll revert Joe's patch > until a correct patch is supplied and reviewed. Well, the simple workaround is to remove the __slots__ field. I don't think it matters here, especially for a singleton. Also, Benjamin's suggestion to make all heap type instances GC-enabled sounds reasonable to me. Regards Antoine.
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