Stefan Krah <stefan-use...@bytereef.org> added the comment: After taking the scenic route through half of the tree[1], I finally found another leak in pythonrun.c. I'm closing #10153, merging those two leaks into the new patch.
Does it look ok? [1] Valgrind stack traces should be approached with caution. ---------- stage: -> patch review title: Memory leak (r70152) -> Refleaks in pythonrun.c Added file: http://bugs.python.org/file19341/pythonrun3.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10157> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
