[Python-Dev] Procedure for adding new public C API (original) (raw)
Masayuki YAMAMOTO ma3yuki.8mamo10 at gmail.com
Mon May 21 21:27:29 EDT 2018
- Previous message (by thread): [Python-Dev] Procedure for adding new public C API
- Next message (by thread): [Python-Dev] My fork lacks a 3.7 branch - can I create it somehow?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks Serhiy, I missed adding PyThread_tss_* to Doc/data/refcounts.dat. I opened a PR to fix it. https://github.com/python/cpython/pull/7038
Regards, Masayuki
2018-05-21 21:41 GMT+09:00 Serhiy Storchaka <storchaka at gmail.com>:
Please don't forgot to perform the following steps when add a new public C API:
* Document it in Doc/c-api/. * Add an entry in the What's New document. * Add it in Doc/data/refcounts.dat. * Add it in PC/python3.def. If you want to include it in the limited API, wrap its declaration with: #if !defined(PyLIMITEDAPI) || PyLIMITEDAPI+0 >= 0x03080000 #endif (use the correct Python version of introducing a feature in the comparison) If you don't want to include it in the limited API, wrap its declaration with: #ifndef PyLIMITEDAPI #endif You are free of adding private C API, but its name should start with Py or PY and its declaration should be wrapped with: #ifndef PyLIMITEDAPI #endif
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ma3yuki. 8mamo10%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180522/e9951d7b/attachment.html>
- Previous message (by thread): [Python-Dev] Procedure for adding new public C API
- Next message (by thread): [Python-Dev] My fork lacks a 3.7 branch - can I create it somehow?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]