Stefan Krah <stefan-use...@bytereef.org> added the comment: Yes, that's basically what I did, but using the latest revision I cannot reproduce the parsetok leak either.
The atexit leak is an old friend (#11826), so I think we can close this one for now. ---------- resolution: -> out of date stage: needs patch -> committed/rejected status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13089> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
