[Python-Dev] Documenting the private C API (was Re: Questions about signal handling.) (original) (raw)
Barry Warsaw barry at python.org
Tue Sep 25 10:31:29 EDT 2018
- Previous message (by thread): [Python-Dev] Documenting the private C API (was Re: Questions about signal handling.)
- Next message (by thread): [Python-Dev] Questions about signal handling.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sep 25, 2018, at 10:08, Jeroen Demeyer <J.Demeyer at UGent.be> wrote:
On 2018-09-25 16:01, Barry Warsaw wrote: Maybe this is better off discussed in doc-sig but I think we need to consider documenting the private C API. Even the public C API is not fully documented. For example, none of the PyCFunction... functions appears in the documentation.
That’s clearly a documentation bug :).
-Barry
-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: <http://mail.python.org/pipermail/python-dev/attachments/20180925/eb7efe88/attachment.sig>
- Previous message (by thread): [Python-Dev] Documenting the private C API (was Re: Questions about signal handling.)
- Next message (by thread): [Python-Dev] Questions about signal handling.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]