-
Notifications
You must be signed in to change notification settings - Fork 45
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
walrus detected incorrectly as keyword argument #250
Comments
I believe this issue represents a limitation of our current syntax checking, which uses Python's built-in compile function, which is tied to the specific Python version that is running To get around this issue (for now), you'll need to either:
|
I feel like the walrus operator should be supported. This was a feature before 3.10... So I'm a bit confused. This is probably using Python pre-3.8. |
Is there a chance that you have a virtualenv or a way of running pre-3.8? Because it might somehow pick up an older environment for some reason. |
As I said 3.10.8 in virtualenv (you can see the interpreter in screenshot bottom right corner) |
Jedi has a separate subprocess, so there was a possibility that that somehow was broken. However I was able to reproduce it with a very simple:
Note that Jedi/Parso can deal with walruses, it's just a small parso error. Created davidhalter/parso#212 for it. |
The text was updated successfully, but these errors were encountered: