Skip to content

gh-103025: fix ctypes doc issues #103026

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 2 commits into from
Mar 25, 2023
Merged

gh-103025: fix ctypes doc issues #103026

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9c5634c
[ctypes doc] 1/ Rectify typo 'varadic' functions to 'variadic'. 2/ Fi…
peterjpxie Mar 25, 2023
34af2aa
Merge branch 'main' into fix-ctypes-doc-issues
peterjpxie Mar 25, 2023
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
6 changes: 3 additions & 3 deletions Doc/library/ctypes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -375,8 +375,8 @@ that they can be converted to the required C data type::

.. _ctypes-calling-variadic-functions:

Calling varadic functions
^^^^^^^^^^^^^^^^^^^^^^^^^
Calling variadic functions
^^^^^^^^^^^^^^^^^^^^^^^^^^

On a lot of platforms calling variadic functions through ctypes is exactly the same
as calling functions with a fixed number of parameters. On some platforms, and in
Expand Down Expand Up @@ -508,7 +508,7 @@ a string pointer and a char, and returns a pointer to a string::

If you want to avoid the ``ord("x")`` calls above, you can set the
:attr:`argtypes` attribute, and the second argument will be converted from a
single character Python bytes object into a C char::
single character Python bytes object into a C char:

.. doctest::

Expand Down