Skip to content

[3.13] Fix a typo in c-api/typeobj.rst (GH-132317) #132464

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 13, 2025
Merged

[3.13] Fix a typo in c-api/typeobj.rst (GH-132317) #132464

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Doc/c-api/typeobj.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -606,12 +606,12 @@
:c:member:`!tp_basicsize` plus N times :c:member:`!tp_itemsize`,
where N is the "length" of the object.

Functions like :c:func:`PyObject_NewVar` will take the value of N as an

Check warning on line 609 in Doc/c-api/typeobj.rst

View workflow job for this annotation

GitHub Actions / Docs / Docs 

c:func reference target not found: PyLong_Export [ref.func]
argument, and store in the instance's :c:member:`~PyVarObject.ob_size` field.
Note that the :c:member:`~PyVarObject.ob_size` field may later be used for
other purposes. For example, :py:type:`int` instances use the bits of
:c:member:`~PyVarObject.ob_size` in an implementation-defined
way; the underlying storage and its size should be acessed using
way; the underlying storage and its size should be accessed using
:c:func:`PyLong_Export`.

.. note::
Expand Down
Loading