➜

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 vstinner
Recipients benjamin.peterson, cstratak, ishcherb, serhiy.storchaka, vstinner
Date 2017-10-06.20:24:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507321473.4.0.213398074469.issue31692@psf.upfronthosting.co.za>
In-reply-to
Content 
My colleague Iryna Shcherbina came to me with this issue. I'm not sure that we really need to support COUNT_ALLOCS. But strangely, it seems simpler to fix bugs rather than guessing if users like this debug mode or not :-)

There are different ways to fix tests to make them passing with COUNT_ALLOCS. As I wrote, I would prefer to add a new Python 2.7 option to explicitly asks to dump allocations statistics: add a new PYTHONSHOWALLOCCOUNT=1 environment variable for example.

What do you think Serhiy? Do you prefer to decorate many 2.7 tests to skip them if COUNT_ALLOCS is used, or to add a new option?

I should try to implement -X showalloccount :-)
History
Date User Action Args
2017-10-06 20:24:33vstinnersetrecipients: + vstinner, benjamin.peterson, serhiy.storchaka, cstratak, ishcherb
2017-10-06 20:24:33vstinnersetmessageid: <1507321473.4.0.213398074469.issue31692@psf.upfronthosting.co.za>
2017-10-06 20:24:33vstinnerlinkissue31692 messages
2017-10-06 20:24:33vstinnercreate