Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

gh-134160: Block multiple module initialization #134773

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 28, 2025
Merged

gh-134160: Block multiple module initialization #134773

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d2ef0c3
gh-134160: Block multiple module initialization
encukou May 27, 2025
c53b208
Update Doc/extending/extending.rst
encukou May 27, 2025
e961fac
Update Doc/extending/extending.rst
AA-Turner May 27, 2025
c562e2e
Apply suggestions from code review
encukou May 28, 2025
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
Update Doc/extending/extending.rst
  • Loading branch information
@encukou
encukou authored May 27, 2025
commit c53b208e16c8c221ad3247c63cc218cb58d64191
2 changes: 1 addition & 1 deletion 2 Doc/extending/extending.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -268,7 +268,7 @@ needed to ensure that it will not be discarded, causing :c:data:`!SpamError` to
become a dangling pointer. Should it become a dangling pointer, C code which
raises the exception could cause a core dump or other unintended side effects.

Also note that there is no :c:func:`Py_DECREF` call to remove this reference.
For now, the :c:func:`Py_DECREF` call to remove this reference is missing.
Even when the Python interpreter shuts down, :c:data:`!SpamError` will not be
garbage-collected. It will "leak".
We did, however, ensure that this will happen at most once per process.
AA-Turner marked this conversation as resolved.
Show resolved Hide resolved
Expand Down
Loading
Morty Proxy This is a proxified and sanitized view of the page, visit original site.