From a788f5ef028d30f03e43932abb4650d502433c83 Mon Sep 17 00:00:00 2001
From: Tim Peters <tim.peters@gmail.com>
Date: Wed, 10 Jul 2002 18:47:03 +0000
Subject: [PATCH] Clarified sys.getobjects() pragmatics.
---
Misc/SpecialBuilds.txt | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/Misc/SpecialBuilds.txt b/Misc/SpecialBuilds.txt
index 3c10f37668..0551c8e8e2 100644
--- a/Misc/SpecialBuilds.txt
+++ b/Misc/SpecialBuilds.txt
@@ -42,12 +42,17 @@ Py_TRACE_REFS implies Py_REF_DEBUG.
Special gimmicks:
sys.getobjects(max[, type])
- Return list of the most-recently allocated max objects, most recently
- allocated first in the list, least-recently allocated last in the
- list. max=0 means no limit on list length. If an optional type
- object is passed, the list is also restricted to objects of that
- type. The return list itself, and some temp objects created just
- to call sys.getobjects(), are excluded from the return list.
+ Return list of the (no more than) max most-recently allocated objects,
+ most recently allocated first in the list, least-recently allocated
+ last in the list. max=0 means no limit on list length.
+ If an optional type object is passed, the list is also restricted to
+ objects of that type.
+ The return list itself, and some temp objects created just to call
+ sys.getobjects(), are excluded from the return list. Note that the
+ list returned is just another object, though, so may appear in the
+ return list the next time you call getobjects(); note that every
+ object in the list is kept alive too, simply by virtue of being in
+ the list.
envar PYTHONDUMPREFS
If this envar exists, Py_Finalize() arranges to print a list of
--
2.40.0