-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-134160: Split extension module init from PyModule docs; emphasize multi-phase init #135126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…asize multi-phase init Document behaviour of single-phase init. Call it "legacy". Reorganize PyModule docs. Move PyInit_modulename docs from the tutorial to reference documentation. Move PyMODINIT_FUNC docs from generic macros to the new page. Add doc stubs for `PYTHON_API_VERSION` & `PYTHON_ABI_VERSION` Remove incorrect refcounts.dat entry for `PyModuleDef_Init`. This removes the "Return value: Borrowed reference." note. Instead, note that the function sometimes returns a borrowed reference, sometimes as strong one. (IMO, it's best to not think of `PyModuleDef` as a `PyObject` at all, and act like it can't be reference-counted.) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From a quick look, though I assume some are existing errors.
Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
…asize multi-phase init (pythonGH-135126) Document behaviour of single-phase init. Call it "legacy". Reorganize PyModule docs. Move PyInit_modulename docs from the tutorial to reference documentation. Move PyMODINIT_FUNC docs from generic macros to the new page. Add doc stubs for `PYTHON_API_VERSION` & `PYTHON_ABI_VERSION` Remove incorrect refcounts.dat entry for `PyModuleDef_Init`. This removes the "Return value: Borrowed reference." note. Instead, note that the function sometimes returns a borrowed reference, sometimes as strong one. (IMO, it's best to not think of `PyModuleDef` as a `PyObject` at all, and act like it can't be reference-counted.) (cherry picked from commit f4bc3a9) Co-authored-by: Petr Viktorin <encukou@gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
GH-135470 is a backport of this pull request to the 3.14 branch. |
#134764 moved a section around; I don't think that's enough.
Split extension module init from
PyModule
docs; emphasize multi-phase initThere's a difference between working with module objects in general
(which just needs garden-variety API docs), and defining the init
function (which covers things like correctly exporting a function
defined by the user, and lots of behaviour that's unrelated to generic
module objects).
Document behaviour of single-phase init. Call it "legacy".
Reorganize
PyModule
docs.Move PyInit_modulename docs from the tutorial, and PyMODINIT_FUNC docs
from the generic macros section, to the new page.
Add docs
Add doc stubs for
PYTHON_API_VERSION
&PYTHON_ABI_VERSION
Remove incorrect
refcounts.dat
entry forPyModuleDef_Init
;instead note that the function sometimes returns a borrowed reference,
sometimes as strong one.
(IMO, it's best to pretend
PyModuleDef
isn't aPyObject
at all,but, reference docs should be correct.)
📚 Documentation preview 📚: https://cpython-previews--135126.org.readthedocs.build/