8000 [3.7] bpo-41455: Provide a link to how the third generation is collected in the GC docs (GH-21703) by miss-islington · Pull Request #21788 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 12, 2020
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Doc/library/gc.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,9 +103,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()
Expand Down
0