bpo-41455: Provide a link to how the third generation is collected in the GC docs (GH-21703)

Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
(cherry picked from commit 82ca8fada1)

Co-authored-by: Yaroslav Pankovych <31005942+P-Alban@users.noreply.github.com>
This commit is contained in:
Miss Islington (bot) 2020-08-08 11:55:45 -07:00 committed by GitHub
parent 66c8996619
commit 105cfb5b18
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

View File

@ -106,9 +106,9 @@ The :mod:`gc` module provides the following functions:
allocations minus the number of deallocations exceeds *threshold0*, collection
starts. Initially only generation ``0`` is examined. If generation ``0`` has
been examined more than *threshold1* times since generation ``1`` has been
examined, then generation ``1`` is examined as well. Similarly, *threshold2*
controls the number of collections of generation ``1`` before collecting
generation ``2``.
examined, then generation ``1`` is examined as well.
With the third generation, things are a bit more complicated,
see `Collecting the oldest generation <https://devguide.python.org/garbage_collector/#collecting-the-oldest-generation>`_ for more information.
.. function:: get_count()