Larry Hastings added the comment: So, this is fixed, but there's some suspicion of a memory leak? If that's true, maybe we could mark this as closed then open a new bug for the leak? This shows up as a big scary "release blocker" against 3.4, and I'm like making releases and stuff.
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18709> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
