[issue14189] C API documentation must document if returned object is a borrowed reference or strong reference

2021-03-21 Thread Irit Katriel
Irit Katriel added the comment: This was fixed for all the functions listed by the OP, except a few that no longer exist AFAICT: Doc/c-api/import.rst: _PyImport_FindExtension Doc/c-api/import.rst: _PyImport_FixupExtension Doc/c-api/init.rst: PyEval_GetCallStats Doc/c-api/int.rst:

[issue14189] C API documentation must document if returned object is a borrowed reference or strong reference

2020-07-04 Thread Joannah Nanjekye
Change by Joannah Nanjekye : -- nosy: +nanjekyejoannah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14189] C API documentation must document if returned object is a borrowed reference or strong reference

2020-06-25 Thread STINNER Victor
Change by STINNER Victor : -- components: +C API title: Documentation for some C APIs is missing clear specification of the type of reference they return -> C API documentation must document if returned object is a borrowed reference or strong reference versions: +Python 3.10 -Python