Lines Matching refs:borrowed

632 *borrowed* references; do not decrement their reference count!
926 not hold on to the object longer than the owner from which it was borrowed.
927 Using a borrowed reference after the owner has disposed of it risks using freed
932 --- in other words, with a borrowed reference you don't run the risk of leaking
934 that there are some subtle situations where in seemingly correct code a borrowed
935 reference can be used after the owner from which it was borrowed has in fact
938 A borrowed reference can be changed into an owned reference by calling
940 reference was borrowed --- it creates a new owned reference, and gives full
969 The function :c:func:`PyImport_AddModule` also returns a borrowed reference, even
982 from the caller.  The caller owns a reference to the object, so the borrowed
984 borrowed reference must be stored or passed on, it must be turned into an owned
997 There are a few situations where seemingly harmless use of a borrowed reference
1014 ``list[1]`` with the value ``0``, and finally prints the borrowed reference.
1050 The second case of problems with a borrowed reference is a variant involving