-
Notifications
You must be signed in to change notification settings - Fork 6
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
# type: ignore leads to AssertionError #3
Comments
Indeed, I can confirm the error. For the time being I've created a branch which reproduces the error - I think the error might boil down to a too-strict assertion, i.e. maybe the code would just work with the assertion disabled. Have you tried running your code with |
The issue seems to be gone with |
Any chance that this will be fixed soon? :) Thanks... |
Yeah, I'm working on this issue (and some related ones that emerged) right now. Feel free to test with current |
I can confirm that the issue is fixed in |
Yes, sorry for the wait! And thanks for the verification. I'll get down to finalize those fixes soon! |
@mbdevpl It would be great if you can make a new release containing this fix. The project I'm working on depends on horast and this issue causes some troubles :-) Many thanks! |
If the following code:
is passed to
horast.parse
, an AssertionError is raised:If I replace
# type: ignore
by normal comment, it works. Also, if# whatever comment
is removed, it works. Tested with horast version 0.3.1. Any ideas? Many thanks!The text was updated successfully, but these errors were encountered: