8000 gh-134160: Use multi-phase init in documentation examples by neonene · Pull Request #134296 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

gh-134160: Use multi-phase init in documentation examples #134296

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

Merged
merged 24 commits into from
May 26, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
typo
  • Loading branch information
neonene authored May 21, 2025
commit bc782883f2ce7a03f3ffe541241c96598373cd5a
4 changes: 2 additions & 2 deletions Doc/extending/extending.rst
Original file line number Diff line number Diff line change
Expand Up @@ -483,8 +483,8 @@ optionally followed by an import of the module::
.. note::

If you need to define *static* extension types rather than heap-allocated
types, the :c:data:`Py_mod_multiple_interpreters` slot in the example should
be ``Py_MOD_MULTIPLE_INTERPRETERS_NOT_SUPPORTED}``. Without it, the module
types, the :c:data:`Py_mod_multiple_interpreters` slot in the examples should
be ``Py_MOD_MULTIPLE_INTERPRETERS_NOT_SUPPORTED``. Without it, the module
can create the same problems as the legacy single-phase initialization, when
removing entries from ``sys.modules`` or importing compiled modules into
multiple interpreters within a process (or following a :c:func:`fork` without an
Expand Down
Loading
0