➜

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 methane
Recipients barry, benjamin.peterson, brainfvck, davin, lukasz.langa, methane, nascheme, pitrou, rhettinger, serhiy.storchaka, tim.peters, vstinner, yselivanov
Date 2017-10-12.00:56:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507769775.86.0.213398074469.issue31558@psf.upfronthosting.co.za>
In-reply-to
Content 
Should gc.freeze() do gc.collect() right before freezing?
Or should we document `gc.collect(); gc.freeze();` idiom?

I don't like `gc.freeze(collect=False)`.
So if there is at least one use case of `gc.freeze()` without `gc.collect()`, I'm +1 on former (current pull request) design.


Other nitpicking: get_freeze_count() or get_frozen_count()?
History
Date User Action Args
2017-10-12 00:56:15methanesetrecipients: + methane, tim.peters, barry, nascheme, rhettinger, pitrou, vstinner, benjamin.peterson, lukasz.langa, serhiy.storchaka, yselivanov, davin, brainfvck
2017-10-12 00:56:15methanesetmessageid: <1507769775.86.0.213398074469.issue31558@psf.upfronthosting.co.za>
2017-10-12 00:56:15methanelinkissue31558 messages
2017-10-12 00:56:15methanecreate