Skip to content

Commit 103ce3d

Browse files
bpo-41455: Provide a link to how the third generation is collected in the GC docs (GH-21703)
Co-authored-by: Pablo Galindo <[email protected]> (cherry picked from commit 82ca8fa) Co-authored-by: Yaroslav Pankovych <[email protected]>
1 parent d910643 commit 103ce3d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Doc/library/gc.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -106,9 +106,9 @@ The :mod:`gc` module provides the following functions:
106106
allocations minus the number of deallocations exceeds *threshold0*, collection
107107
starts. Initially only generation ``0`` is examined. If generation ``0`` has
108108
been examined more than *threshold1* times since generation ``1`` has been
109-
examined, then generation ``1`` is examined as well. Similarly, *threshold2*
110-
controls the number of collections of generation ``1`` before collecting
111-
generation ``2``.
109+
examined, then generation ``1`` is examined as well.
110+
With the third generation, things are a bit more complicated,
111+
see `Collecting the oldest generation <https://devguide.python.org/garbage_collector/#collecting-the-oldest-generation>`_ for more information.
112112

113113

114114
.. function:: get_count()

0 commit comments

Comments
 (0)