[issue18017] ctypes.PyDLL documentation

Eryk Sun added the comment: I think the documentation of ctypes.PyDLL and ctypes.pythonapi is good enough as is. -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker

[issue18017] ctypes.PyDLL documentation

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18017] ctypes.PyDLL documentation

marc added the comment: I think the problem was a combination of two issues. First, the warning in 16.17.2.2 is a bit hidden. Kind of squeezed in between CDLL, etc and PyDLL. In contrast, 16.17.2.4 does a much better job, because it restates the fact that the GIL is released at each and

[issue18017] ctypes.PyDLL documentation

Mark Lawrence added the comment: @Marc can you prepare a patch for this issue? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18017 ___

[issue18017] ctypes.PyDLL documentation

eryksun added the comment: 16.17.2.2 already has a warning after it introduces CDLL, OleDLL, and WinDLL: The Python global interpreter lock is released before calling any function exported by these libraries, and reacquired afterwards. It links to the glossary entry:

[issue18017] ctypes.PyDLL documentation

New submission from Marc Brünink: The documentation for is not very clear regarding the usage of CDLL and PyDLL. Especially it is not obvious that you should use PyDLL whenever you call any function of the Python/C API. Since calling a Python/C API function without owning the GIL will most