Sorry, something went wrong.
|
No, this is not correct, we also need to check __dictoffset__ as well. For __dict__ case. |
Sorry, something went wrong.
|
Ubuntu failures are not related, there are some network problems right now |
Sorry, something went wrong.
There was a problem hiding this comment.
I think this fix is correct; some suggestions and a question.
Sorry, something went wrong.
There was a problem hiding this comment.
This looks fine to me. Sorry I didn't see the notification sooner that you requested another review!
I still think the best version of this might look at __weakrefoffset__ and __dictrefoffset__ always to decide on those two slots, but I agree that's an edge case and can be handled separately; this is still a clear improvement and fixes the original bug.
Sorry, something went wrong.
|
Thanks @sobolevn for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
Sorry, something went wrong.
|
GH-118821 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
|
GH-118822 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
Looks like that classes with __weakrefoffset__ == 0 does not need to add __weakref__ slot to existing super ones.