From: Brett Cannon Date: Thu, 29 Jan 2009 00:54:11 +0000 (+0000) Subject: Clarify some __del__ stuff. X-Git-Tag: v2.7a1~2173 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5b0d5531f2b688dfff2eaac529a9bb57c4ee839d;p=python Clarify some __del__ stuff. --- diff --git a/Doc/reference/datamodel.rst b/Doc/reference/datamodel.rst index dbcc9a1c90..5b6f1e8243 100644 --- a/Doc/reference/datamodel.rst +++ b/Doc/reference/datamodel.rst @@ -1257,7 +1257,9 @@ Basic customization is printed to ``sys.stderr`` instead. Also, when :meth:`__del__` is invoked in response to a module being deleted (e.g., when execution of the program is done), other globals referenced by the :meth:`__del__` method may already have - been deleted. For this reason, :meth:`__del__` methods should do the absolute + been deleted or in the process of being torn down (e.g. the import + machinery shutting down). For this reason, :meth:`__del__` methods + should do the absolute minimum needed to maintain external invariants. Starting with version 1.5, Python guarantees that globals whose name begins with a single underscore are deleted from their module before other globals are deleted; if no other