This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author larry
Recipients Arfrever, abn, barry, benjamin.peterson, christian.heimes, dstufft, georg.brandl, larry, python-dev, sYnfo, vstinner
Date 2013-10-19.01:17:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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.
Date User Action Args
2013-10-19 01:17:54larrysetrecipients: + larry, barry, georg.brandl, vstinner, christian.heimes, benjamin.peterson, Arfrever, python-dev, dstufft, abn, sYnfo
2013-10-19 01:17:53larrysetmessageid: <>
2013-10-19 01:17:53larrylinkissue18709 messages
2013-10-19 01:17:53larrycreate