-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
gh-119213: Be More Careful About _PyArg_Parser.kwtuple Across Interpreters #119331
Changes from all commits
f0f080b
c288a71
35abdad
e179765
e6f78fb
dbf113b
9b73c3d
6b9c436
9157ad5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
Non-builtin modules built with argument clinic were crashing if used in a | ||
subinterpreter before the main interpreter. The objects that were causing | ||
the problem by leaking between interpreters carelessly have been fixed. |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
Is doing this before checking
if (kwtuple == NULL)
the right way?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.
Yeah, we want to clean up the temporary tstate regardless of the outcome of
new_kwtuple()
.