-
Notifications
You must be signed in to change notification settings - Fork 779
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
Borrowed<PyType>::name
is not consistent
#4055
Comments
IIRC, we made the concicous decision to expose |
The issue is that it's hard (if not impossible) to emulate With That's why I think we cannot expose |
Isn't using what you implemented as |
I feel a little stupid 😅 However, we have to consider that most of the calls to this new Anyway, I can modify my PR if you judge that it is worth it. |
This got resolved in #4196 |
With
#[cfg(not(any(Py_LIMITED_API, PyPy)))]
,Borrowed<'a, '_, PyType>::name
implementation delegates totp_name
.However,
tp_name
is not consistent.For pure Python types
Borrowed<'a, '_, PyType>::name
returns different result if compiled with or withoutabi3
feature.Solution
Make
Borrowed<'a, '_, PyType>::name
follow__name__
behavior, and exposeBorrowed<'a, '_, PyType>::module
.I will open a PR.
The text was updated successfully, but these errors were encountered: