[Python-Dev] Documenting the private C API (was Re: Questions about signal handling.) (original) (raw)
Barry Warsaw barry at python.org
Tue Sep 25 11:53:08 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] Documenting the private C API (was Re: Questions about signal handling.)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sep 25, 2018, at 11:28, Victor Stinner <vstinner at redhat.com> wrote:
But if we have a separated documented for CPython internals, why not documenting private functions. At least, I would prefer to not put it at the same place an the public C API. (At least, a different directory.)
I like the idea of an “internals” C API documentation, separate from the public API.
-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/f642bcc7/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] Documenting the private C API (was Re: Questions about signal handling.)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]