From a4c8c47961305487ef6c40a6d882bb956f2c5a0b Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Fri, 31 Oct 2014 10:38:49 +0100 Subject: #22613: remaining corrections in extending/reference docs (thanks Jacques Ducasse) --- Doc/extending/extending.rst | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) (limited to 'Doc/extending') diff --git a/Doc/extending/extending.rst b/Doc/extending/extending.rst index a3bf2656ed..e78fe0c4b1 100644 --- a/Doc/extending/extending.rst +++ b/Doc/extending/extending.rst @@ -857,11 +857,8 @@ reclaim the memory belonging to any objects in a reference cycle, or referenced from the objects in the cycle, even though there are no further references to the cycle itself. -The cycle detector is able to detect garbage cycles and can reclaim them so long -as there are no finalizers implemented in Python (:meth:`__del__` methods). -When there are such finalizers, the detector exposes the cycles through the -:mod:`gc` module (specifically, the :attr:`~gc.garbage` variable in that module). -The :mod:`gc` module also exposes a way to run the detector (the +The cycle detector is able to detect garbage cycles and can reclaim them. +The :mod:`gc` module exposes a way to run the detector (the :func:`~gc.collect` function), as well as configuration interfaces and the ability to disable the detector at runtime. The cycle detector is considered an optional component; though it is included by default, -- cgit v1.2.1