-
-
Notifications
You must be signed in to change notification settings - Fork 33.2k
gh-123504: Fix regression in _tkinter
initializer
#123662
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
(@encukou, this needs |
You can @ either me or @Eclips4 for skip news requests since we are triagers, or we'll just see whether this is needed or not when we'll look at the PR. |
I would, but Petr specifically requested that I ping him for label changes (he's "mentoring" me for triage membership). |
Does that look alright? |
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.
Sounds good! If I were to nitpick I would have (in the previous PR that I wasn't able to comment since it was merged before):
Py_UNUSED(module)
in themodule_traverse
signaturePy_UNUSED(mod)
in themodule_clear
signature(void)module_clear((PyObject *)mod);
inmodule_free
- Renamed the functions to
_tkintermodule_{clear,traverse,free}
.
You could do those cosmetic changes if you want but otherwise it's fine.
…/cpython into tkinter-regression
I'm going to leave the names as is, we can change them if we decide to migrate tkinter over to PEP 489 |
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.
LGTM.
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.
LGTM.
cc @serhiy-storchaka
_tkinter
leaks type references on initialization #123504