Skip to content

[3.14] gh-114150: Clarify that ctypes.PYFUNCTYPE can release the GIL during the call (GH-114151) #159735

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
ZeroIntensity merged 1 commit into from
Oct 19, 2026
+5 −1
Merged

[3.14] gh-114150: Clarify that ctypes.PYFUNCTYPE can release the GIL during the call (GH-114151) #159735

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
6 changes: 5 additions & 1 deletion Doc/library/ctypes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1968,7 +1968,11 @@ See :ref:`ctypes-callback-functions` for examples.
.. function:: PYFUNCTYPE(restype, *argtypes)

The returned function prototype creates functions that use the Python calling
convention. The function will *not* release the GIL during the call.
convention. Unlike :func:`CFUNCTYPE` and :func:`WINFUNCTYPE`, ctypes does
*not* release the GIL before calling the foreign function, so the function
may safely use the Python C API. Note that this does not prevent the GIL
from being released *during* the call.


Function prototypes created by these factory functions can be instantiated in
different ways, depending on the type and number of the parameters in the call:
Expand Down
Loading