-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
INTERNALERROR> tokenize.TokenError: 'unexpected EOF in multi-line statement'
when trying to report a missing fixture in Hy
#12846
Comments
Given that We do already catch various exceptions there: pytest/src/_pytest/fixtures.py Lines 814 to 818 in 6486c3f
If it's as easy as catching |
I'm not sure how much of the |
I'd be happy to accept a PR, but don't really consider this a Pytest bug - if we happen to support Hy that's lovely, but it's not something we advertise or promise to anyone. |
Per the docs, I think that Hy should probably ensure that |
@Zac-HD But the documentation doesn't say |
In this example, pytest hits an internal error when trying to report "fixture 'f' not found". I don't know how to reproduce it without Hy; I suspect the problem is that
_pytest.fixtures.formatrepr
callsinspect.getsourcelines
without any provisions for the possibility that there isn't real Python code in the source file. I notice that the internal error doesn't occur if you replace the[
at the beginning of the program withx
.The text was updated successfully, but these errors were encountered: