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 rbcollins
Recipients ezio.melotti, michael.foord, pitrou, rbcollins, serhiy.storchaka, vstinner
Date 2015-04-01.20:30:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'd like to see a definite profile of a bloated stdlib test process before we assume we know the issue - the usual leak I see in test code is used test objects, and I'm not sure we've ported the usual fix for that into unittest yet (we should).

As far as linecache is concerned, we shouldn't be triggering linecache population except when a traceback is actually rendered, and so on a passing test run there should be little hitting it at all outside of tests that actually test rendering of tracebacks.
Date User Action Args
2015-04-01 20:30:15rbcollinssetrecipients: + rbcollins, pitrou, vstinner, ezio.melotti, michael.foord, serhiy.storchaka
2015-04-01 20:30:15rbcollinssetmessageid: <>
2015-04-01 20:30:15rbcollinslinkissue23839 messages
2015-04-01 20:30:15rbcollinscreate