-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-107810: Improve DeprecationWarning for metaclasses with custom tp_new #107834
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
Misc/NEWS.d/next/C API/2023-08-10-11-12-25.gh-issue-107810.oJ40Qx.rst
Outdated
Show resolved
Hide resolved
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. Let's wait for the Petr's opinion.
Co-authored-by: Kirill Podoprigora <kirill.bast9@mail.ru>
Thank you for the PR! The wording looks weird to me though. Could you split it to two sentences, one about the concrete type and one about the behaviour being deprecated?
|
@encukou Can this be backported to |
This comment was marked as off-topic.
This comment was marked as off-topic.
Buildbot failure unrelated. |
GH-107864 is a backport of this pull request to the 3.12 branch. |
…om tp_new (pythonGH-107834) (cherry picked from commit 16dcce2) Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com> Co-authored-by: Kirill Podoprigora <kirill.bast9@mail.ru>
Thanks @Eclips4 for the idea!
If accepted, it would be great if this change could be backported to
3.12
. If not into3.12.0
, than3.12.1
.As example, for
protobuf
the warning would change as such