2019-05-17 06:55:34 -03:00
|
|
|
.. highlight:: c
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
|
|
|
|
.. _countingrefs:
|
|
|
|
|
|
|
|
******************
|
|
|
|
Reference Counting
|
|
|
|
******************
|
|
|
|
|
2022-12-07 10:22:38 -04:00
|
|
|
The functions and macros in this section are used for managing reference counts
|
|
|
|
of Python objects.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
|
2022-10-15 11:56:14 -03:00
|
|
|
.. c:function:: Py_ssize_t Py_REFCNT(PyObject *o)
|
|
|
|
|
|
|
|
Get the reference count of the Python object *o*.
|
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Note that the returned value may not actually reflect how many
|
|
|
|
references to the object are actually held. For example, some
|
2023-11-17 10:09:19 -04:00
|
|
|
objects are :term:`immortal` and have a very high refcount that does not
|
2023-08-07 18:40:59 -03:00
|
|
|
reflect the actual number of references. Consequently, do not rely
|
|
|
|
on the returned value to be accurate, other than a value of 0 or 1.
|
|
|
|
|
2022-10-15 11:56:14 -03:00
|
|
|
Use the :c:func:`Py_SET_REFCNT()` function to set an object reference count.
|
|
|
|
|
|
|
|
.. versionchanged:: 3.10
|
|
|
|
:c:func:`Py_REFCNT()` is changed to the inline static function.
|
|
|
|
|
2024-03-07 04:05:03 -04:00
|
|
|
.. versionchanged:: 3.11
|
|
|
|
The parameter type is no longer :c:expr:`const PyObject*`.
|
|
|
|
|
2022-10-15 11:56:14 -03:00
|
|
|
|
|
|
|
.. c:function:: void Py_SET_REFCNT(PyObject *o, Py_ssize_t refcnt)
|
|
|
|
|
|
|
|
Set the object *o* reference counter to *refcnt*.
|
|
|
|
|
2023-12-01 10:50:16 -04:00
|
|
|
On :ref:`Python build with Free Threading <free-threading-build>`, if
|
|
|
|
*refcnt* is larger than ``UINT32_MAX``, the object is made :term:`immortal`.
|
|
|
|
|
2023-11-17 10:09:19 -04:00
|
|
|
This function has no effect on :term:`immortal` objects.
|
2023-08-07 18:40:59 -03:00
|
|
|
|
2022-10-15 11:56:14 -03:00
|
|
|
.. versionadded:: 3.9
|
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
.. versionchanged:: 3.12
|
|
|
|
Immortal objects are not modified.
|
|
|
|
|
2022-10-15 11:56:14 -03:00
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
.. c:function:: void Py_INCREF(PyObject *o)
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Indicate taking a new :term:`strong reference` to object *o*,
|
|
|
|
indicating it is in use and should not be destroyed.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2023-11-17 10:09:19 -04:00
|
|
|
This function has no effect on :term:`immortal` objects.
|
|
|
|
|
2020-11-09 08:40:47 -04:00
|
|
|
This function is usually used to convert a :term:`borrowed reference` to a
|
|
|
|
:term:`strong reference` in-place. The :c:func:`Py_NewRef` function can be
|
|
|
|
used to create a new :term:`strong reference`.
|
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
When done using the object, release is by calling :c:func:`Py_DECREF`.
|
|
|
|
|
2020-11-09 08:40:47 -04:00
|
|
|
The object must not be ``NULL``; if you aren't sure that it isn't
|
|
|
|
``NULL``, use :c:func:`Py_XINCREF`.
|
2020-11-05 10:02:12 -04:00
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Do not expect this function to actually modify *o* in any way.
|
2024-09-17 10:02:14 -03:00
|
|
|
For at least :pep:`some objects <0683>`,
|
2023-08-07 18:40:59 -03:00
|
|
|
this function has no effect.
|
|
|
|
|
|
|
|
.. versionchanged:: 3.12
|
|
|
|
Immortal objects are not modified.
|
|
|
|
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
.. c:function:: void Py_XINCREF(PyObject *o)
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Similar to :c:func:`Py_INCREF`, but the object *o* can be ``NULL``,
|
|
|
|
in which case this has no effect.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2020-11-05 10:02:12 -04:00
|
|
|
See also :c:func:`Py_XNewRef`.
|
|
|
|
|
|
|
|
|
|
|
|
.. c:function:: PyObject* Py_NewRef(PyObject *o)
|
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Create a new :term:`strong reference` to an object:
|
|
|
|
call :c:func:`Py_INCREF` on *o* and return the object *o*.
|
2020-11-09 08:40:47 -04:00
|
|
|
|
|
|
|
When the :term:`strong reference` is no longer needed, :c:func:`Py_DECREF`
|
2023-08-07 18:40:59 -03:00
|
|
|
should be called on it to release the reference.
|
2020-11-05 10:02:12 -04:00
|
|
|
|
2020-11-09 08:40:47 -04:00
|
|
|
The object *o* must not be ``NULL``; use :c:func:`Py_XNewRef` if *o* can be
|
|
|
|
``NULL``.
|
2020-11-05 10:02:12 -04:00
|
|
|
|
|
|
|
For example::
|
|
|
|
|
|
|
|
Py_INCREF(obj);
|
|
|
|
self->attr = obj;
|
|
|
|
|
|
|
|
can be written as::
|
|
|
|
|
|
|
|
self->attr = Py_NewRef(obj);
|
|
|
|
|
2020-11-09 08:40:47 -04:00
|
|
|
See also :c:func:`Py_INCREF`.
|
|
|
|
|
2020-11-05 10:02:12 -04:00
|
|
|
.. versionadded:: 3.10
|
|
|
|
|
|
|
|
|
|
|
|
.. c:function:: PyObject* Py_XNewRef(PyObject *o)
|
|
|
|
|
|
|
|
Similar to :c:func:`Py_NewRef`, but the object *o* can be NULL.
|
|
|
|
|
|
|
|
If the object *o* is ``NULL``, the function just returns ``NULL``.
|
|
|
|
|
|
|
|
.. versionadded:: 3.10
|
|
|
|
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
.. c:function:: void Py_DECREF(PyObject *o)
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Release a :term:`strong reference` to object *o*, indicating the
|
|
|
|
reference is no longer used.
|
2020-11-09 08:40:47 -04:00
|
|
|
|
2023-11-17 10:09:19 -04:00
|
|
|
This function has no effect on :term:`immortal` objects.
|
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Once the last :term:`strong reference` is released
|
|
|
|
(i.e. the object's reference count reaches 0),
|
|
|
|
the object's type's deallocation
|
2020-11-09 08:40:47 -04:00
|
|
|
function (which must not be ``NULL``) is invoked.
|
|
|
|
|
|
|
|
This function is usually used to delete a :term:`strong reference` before
|
|
|
|
exiting its scope.
|
|
|
|
|
|
|
|
The object must not be ``NULL``; if you aren't sure that it isn't ``NULL``,
|
|
|
|
use :c:func:`Py_XDECREF`.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Do not expect this function to actually modify *o* in any way.
|
2024-09-17 10:02:14 -03:00
|
|
|
For at least :pep:`some objects <683>`,
|
2023-08-07 18:40:59 -03:00
|
|
|
this function has no effect.
|
|
|
|
|
2007-08-15 11:28:22 -03:00
|
|
|
.. warning::
|
|
|
|
|
|
|
|
The deallocation function can cause arbitrary Python code to be invoked (e.g.
|
2023-07-23 06:23:44 -03:00
|
|
|
when a class instance with a :meth:`~object.__del__` method is deallocated). While
|
2007-08-15 11:28:22 -03:00
|
|
|
exceptions in such code are not propagated, the executed code has free access to
|
|
|
|
all Python global variables. This means that any object that is reachable from
|
2010-10-06 07:11:56 -03:00
|
|
|
a global variable should be in a consistent state before :c:func:`Py_DECREF` is
|
2007-08-15 11:28:22 -03:00
|
|
|
invoked. For example, code to delete an object from a list should copy a
|
|
|
|
reference to the deleted object in a temporary variable, update the list data
|
2010-10-06 07:11:56 -03:00
|
|
|
structure, and then call :c:func:`Py_DECREF` for the temporary variable.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
.. versionchanged:: 3.12
|
|
|
|
Immortal objects are not modified.
|
|
|
|
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
.. c:function:: void Py_XDECREF(PyObject *o)
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Similar to :c:func:`Py_DECREF`, but the object *o* can be ``NULL``,
|
|
|
|
in which case this has no effect.
|
|
|
|
The same warning from :c:func:`Py_DECREF` applies here as well.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
|
|
|
|
2010-10-06 07:11:56 -03:00
|
|
|
.. c:function:: void Py_CLEAR(PyObject *o)
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Release a :term:`strong reference` for object *o*.
|
|
|
|
The object may be ``NULL``, in
|
2007-08-15 11:28:22 -03:00
|
|
|
which case the macro has no effect; otherwise the effect is the same as for
|
2019-10-30 07:03:20 -03:00
|
|
|
:c:func:`Py_DECREF`, except that the argument is also set to ``NULL``. The warning
|
2010-10-06 07:11:56 -03:00
|
|
|
for :c:func:`Py_DECREF` does not apply with respect to the object passed because
|
2019-10-30 07:03:20 -03:00
|
|
|
the macro carefully uses a temporary variable and sets the argument to ``NULL``
|
2023-08-07 18:40:59 -03:00
|
|
|
before releasing the reference.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
It is a good idea to use this macro whenever releasing a reference
|
|
|
|
to an object that might be traversed during garbage collection.
|
2007-08-15 11:28:22 -03:00
|
|
|
|
2022-12-07 10:22:38 -04:00
|
|
|
.. versionchanged:: 3.12
|
|
|
|
The macro argument is now only evaluated once. If the argument has side
|
|
|
|
effects, these are no longer duplicated.
|
|
|
|
|
|
|
|
|
2022-05-18 05:42:05 -03:00
|
|
|
.. c:function:: void Py_IncRef(PyObject *o)
|
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Indicate taking a new :term:`strong reference` to object *o*.
|
|
|
|
A function version of :c:func:`Py_XINCREF`.
|
2022-05-18 05:42:05 -03:00
|
|
|
It can be used for runtime dynamic embedding of Python.
|
|
|
|
|
|
|
|
|
|
|
|
.. c:function:: void Py_DecRef(PyObject *o)
|
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Release a :term:`strong reference` to object *o*.
|
|
|
|
A function version of :c:func:`Py_XDECREF`.
|
2022-05-18 05:42:05 -03:00
|
|
|
It can be used for runtime dynamic embedding of Python.
|
2022-12-07 10:22:38 -04:00
|
|
|
|
|
|
|
|
|
|
|
.. c:macro:: Py_SETREF(dst, src)
|
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
Macro safely releasing a :term:`strong reference` to object *dst*
|
|
|
|
and setting *dst* to *src*.
|
2022-12-07 10:22:38 -04:00
|
|
|
|
|
|
|
As in case of :c:func:`Py_CLEAR`, "the obvious" code can be deadly::
|
|
|
|
|
|
|
|
Py_DECREF(dst);
|
|
|
|
dst = src;
|
|
|
|
|
|
|
|
The safe way is::
|
|
|
|
|
|
|
|
Py_SETREF(dst, src);
|
|
|
|
|
2023-08-07 18:40:59 -03:00
|
|
|
That arranges to set *dst* to *src* _before_ releasing the reference
|
|
|
|
to the old value of *dst*, so that any code triggered as a side-effect
|
|
|
|
of *dst* getting torn down no longer believes *dst* points
|
|
|
|
to a valid object.
|
2022-12-07 10:22:38 -04:00
|
|
|
|
|
|
|
.. versionadded:: 3.6
|
|
|
|
|
|
|
|
.. versionchanged:: 3.12
|
|
|
|
The macro arguments are now only evaluated once. If an argument has side
|
|
|
|
effects, these are no longer duplicated.
|
|
|
|
|
|
|
|
|
|
|
|
.. c:macro:: Py_XSETREF(dst, src)
|
|
|
|
|
|
|
|
Variant of :c:macro:`Py_SETREF` macro that uses :c:func:`Py_XDECREF` instead
|
|
|
|
of :c:func:`Py_DECREF`.
|
|
|
|
|
|
|
|
.. versionadded:: 3.6
|
|
|
|
|
|
|
|
.. versionchanged:: 3.12
|
|
|
|
The macro arguments are now only evaluated once. If an argument has side
|
|
|
|
effects, these are no longer duplicated.
|