From: Fred Drake Date: Thu, 29 Nov 2001 07:16:19 +0000 (+0000) Subject: Clarify the description of the creation of an owned reference from an API X-Git-Tag: v2.2.1c1~649 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=92024d1a99dff25d5a1e53e39292cbfb30d2a226;p=python Clarify the description of the creation of an owned reference from an API function. This closes SF bug #486657. --- diff --git a/Doc/ext/extending.tex b/Doc/ext/extending.tex index 6cd1137fd9..e78e1d1f4b 100644 --- a/Doc/ext/extending.tex +++ b/Doc/ext/extending.tex @@ -1291,11 +1291,11 @@ transferred with the reference or not. Most functions that return a reference to an object pass on ownership with the reference. In particular, all functions whose function it is to create a new object, such as \cfunction{PyInt_FromLong()} and -\cfunction{Py_BuildValue()}, pass ownership to the receiver. Even if in -fact, in some cases, you don't receive a reference to a brand new -object, you still receive ownership of the reference. For instance, -\cfunction{PyInt_FromLong()} maintains a cache of popular values and can -return a reference to a cached item. +\cfunction{Py_BuildValue()}, pass ownership to the receiver. Even if +the object is not actually new, you still receive ownership of a new +reference to that object. For instance, \cfunction{PyInt_FromLong()} +maintains a cache of popular values and can return a reference to a +cached item. Many functions that extract objects from other objects also transfer ownership with the reference, for instance