STINNER Victor added the comment: Charles: "OK, you fixed what broke us before. If I revert our fixes the problem goes away. So, thanks I guess ;) You can close this."
Cool, happy to read that the issue was fixed :-) If you missed it, the whole mess were backward compatibility when I extended the warnings API (only internally currently) to implement a new feature: https://docs.python.org/dev/whatsnew/3.6.html#warnings ResourceWarning are now displayed with a traceback where the object was allocated when tracemalloc is enabled. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28897> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
