Author steve.dower
Recipients eric.snow, ncoghlan, paul.moore, pjna, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-11-15.17:22:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510766550.79.0.213398074469.issue32026@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think the refleak handling would detect leaks across PyInitialize/PyFinalize calls anyway.

Really, we probably just need to loop Initialize/Finalize a few hundred times and measure the memory usage of the process before/after. That will handle a range of leaks, though it doesn't necessarily help us track them down.
History
Date User Action Args
2017-11-15 17:22:30steve.dowersetrecipients: + steve.dower, paul.moore, ncoghlan, vstinner, tim.golden, eric.snow, zach.ware, pjna
2017-11-15 17:22:30steve.dowersetmessageid: <1510766550.79.0.213398074469.issue32026@psf.upfronthosting.co.za>
2017-11-15 17:22:30steve.dowerlinkissue32026 messages
2017-11-15 17:22:30steve.dowercreate