[issue17243] The changes made for issue 4074 should be documented

Change by Irit Katriel : -- stage: needs patch -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue17243] The changes made for issue 4074 should be documented

Irit Katriel added the comment: I think this has been fixed here in PR21703. -- nosy: +iritkatriel resolution: -> duplicate status: open -> pending superseder: -> Python Devguide differs from python docs ___ Python tracker

[issue17243] The changes made for issue 4074 should be documented

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17243] The changes made for issue 4074 should be documented

Martin v. Löwis added the comment: No. There is no responsibility to do anything in an open source project. -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17243 ___

[issue17243] The changes made for issue 4074 should be documented

Mark Lawrence added the comment: Presumably the responsibility for this lies with the person who made the changes for #4074 ? -- nosy: +BreamoreBoy versions: +Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org

[issue17243] The changes made for issue 4074 should be documented

Changes by Ezio Melotti ezio.melo...@gmail.com: -- assignee: - docs@python components: +Documentation nosy: +docs@python type: behavior - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17243

[issue17243] The changes made for issue 4074 should be documented

New submission from R. David Murray: The section of the reference on the gc module goes into some detail on what the thresholds control and when collections are run, but does not currently document the backoff algorithm used when deciding whether or not to collect generation 2. This should