-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add type_check to _check() #5095
base: main
Are you sure you want to change the base?
Conversation
Welcome to the common RustPython development rabbit hole. Well, I only have general debug advices. It can be either a bug here or combination of other incompatabilty issues there - because getset is shown in error message, I suspect our incomplete getset_descriptor implementation may be releated. I think the trial was really good. I am currently on vacation. I can try a quick look, but not able to look deep down stuff for a while. (To be honest, usually not very helpful for these kind of problems even if I do that) |
Alright, I'll keep digging deeper. Have a nice vacation! |
@dannasman Do you have a specific goal to achieve? Otherwise looking around similar issues may be helpful. I also have many abandoned patches when I got stucked https://github.com/RustPython/RustPython/pulls/youknowone |
I was searching for places where PyObject_TypeCheck should be used in the code and found the |
Hi!
After implementing
type_check
(#5091) I tried to add thetype_check
call in_check
function by following the CPython implementation. I also modifieddescr_get
function ofPyGetSet
based on its CPython counterpart. These modifications cause the code to panic and I am not quite sure why. Any thoughts?