-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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
3.12.0b4 Backwards incompatible change with reassignment of cls.__new__
and super()
#106917
Comments
Thanks for this report!
Note that This simplified and de-sugared repro works in 3.11, but fails in a similar way to the OP in main and 3.12:
The double call to What we have in these examples is a "class-mode" super() call (e.g. In a class-mode super() call (just like for a normal lookup directly on a class), we do not pass an instance to the descriptor-getter, only a type (e.g. The bug here is that the Fix coming shortly. |
…ds (pythonGH-106977). (cherry picked from commit e5d5522) Co-authored-by: Carl Meyer <carl@oddbird.net>
Bug report
Noticed this while testing
3.12.0b4
. While in my particular case I can work around it, it never the less is a change in behavior to3.11
.Without
cls.__new__ = cls.__new__
I bisected the issue to #103497.
/CC: @carljm
Your environment
3.120b4
Linked PRs
The text was updated successfully, but these errors were encountered: