| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
CI Failure came from successful test.
test_subclass (test.test_bool.BoolTest) ... unexpected success
Because you fixed the bug, you can remove @unittest.expectedFailure decorator from the test.
Thank you!
Sorry, something went wrong.
|
I found the following issue in test_ast.py. But I'm sure if it is related to my code. It seems that typ in call_slot_new is set to object instead of Constant for some reason. |
Sorry, something went wrong.
| } | ||
| } | ||
| if let Some(ref basetype) = staticbase { | ||
| if !PyType::subclasscheck(basetype.to_owned(), typ.to_owned()) { |
There was a problem hiding this comment.
PyType_IsSubtype in CPython is same to fast_issubclass in RustPython
Sorry, something went wrong.
|
Hey @garychia do you still have time/want to work on this? |
Sorry, something went wrong.
|
Hi, @DimitrisJim! I was struggling to solve the problem that happens when running the test_ast test as I mentioned before. Based on my observation, RustPython tried to construct an N object by using object.__new__, which is not safe. But I have no idea why it behaved this way and whether it relates to my code. RustPython/Lib/test/test_ast.py Lines 521 to 528 in bbd8fb2 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Related to #3692

This implementation is based on the following code from CPython.
https://github.com/python/cpython/blob/206f05a46b426eb374f724f8e7cd42f2f9643bb8/Objects/typeobject.c#L7685-L7700