-
Notifications
You must be signed in to change notification settings - Fork 769
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
PyEllipsis and PyNotImplemented new get_bound api #3797
PyEllipsis and PyNotImplemented new get_bound api #3797
Conversation
0774e25
to
8388b14
Compare
CodSpeed Performance ReportMerging #3797 will degrade performances by 10.75%Comparing Summary
Benchmarks breakdown
|
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.
Thanks, overall looks good! Just a couple of tiny adjustments that I'd like to see...
(I also notice now that I missed we didn't do this for the PyNone
change earlier, it might be nice to go back and do that either as part of this PR or a separate follow-up.)
Done |
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.
Perfect, thanks!
@@ -15,12 +15,12 @@ impl PyNone { | |||
not(feature = "gil-refs"), | |||
deprecated( | |||
since = "0.21.0", | |||
note = "`PyNone::get` will be replaced by `PyBool::get_bound` in a future PyO3 version" | |||
note = "`PyNone::get` will be replaced by `PyNone::get_bound` in a future PyO3 version" |
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.
Ah good catch! 👍
Parts of #3684
This adds
get_bound
method toPyEllipsis
andPyNotImplemented