Should we show syntax errors by default? #2234
Replies: 5 comments 1 reply
For that it might help to include the Python version in the syntax error messages, so that the user immediately knows that it might be a config thing, and not a syntax thing. So something like "... is not valid in Python 3.9". |
|
Another vote for showing Python syntax errors by default. https://kiro.dev/blog/empowering-kiro-with-ide-diagnostics/
|
|
Starting in 0.52.0 next week, Pyrefly will show syntax errors in |
|
Awesome! Should we keep this discussion open in case the community has feedback? ie. more on by default or issues? |
|
Starting in 0.60.0, we show |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Pyrefly has 4 type checking modes for the IDE:
We're considering making
defaultanderror-missing-importsalso show diagnostics for syntax errors, even on projects w/o a pyrefly.toml.The pros are:
The cons are:
Collecting feedback till 2/1
3 votes ·
All reactions