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 brett.cannon, fijall, lemburg, ned.deily, pitrou, python-dev, rhettinger, serhiy.storchaka, steven.daprano, tim.peters, vstinner
Date 2016-10-18.16:02:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476806557.97.0.520904983871.issue28240@psf.upfronthosting.co.za>
In-reply-to
Content
Steven D'Aprano:
>> * Don't disable the garbage collector anymore! Disabling the GC is not 
>> fair: real applications use it.

> But that's just adding noise: you're not timing code snippet, you're 
timing code snippet plus garbage collector.
>
> I disagree with this change, although I would accept it if there was an 
optional flag to control the gc.

IMO it's a lie to display the minimum timing with the garbage collector disabled. The garbage collector is enabled in all applications.
History
Date User Action Args
2016-10-18 16:02:38vstinnersetrecipients: + vstinner, lemburg, tim.peters, brett.cannon, rhettinger, pitrou, ned.deily, steven.daprano, fijall, python-dev, serhiy.storchaka
2016-10-18 16:02:37vstinnersetmessageid: <1476806557.97.0.520904983871.issue28240@psf.upfronthosting.co.za>
2016-10-18 16:02:37vstinnerlinkissue28240 messages
2016-10-18 16:02:37vstinnercreate