-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Lost linting on change after last update to vscode along vscode-python #9778
Comments
@AjawadMahmoud, thanks for letting us know about this. We will take a look as soon as we can. |
Just to make sure I understood, you have Please provide the content of the "Python Language Server" output panel. What happens if you change "python.jediEnabled" to Also, keep in mind that the "python.linting.lintOnTextChange" setting has been deprecated for quite a while. That said, nothing related has changed recently in the extension. |
I've noticed the same problem. Here is my Python Language Server output if that helps:
|
Seems to be related to #9649. Rolling back to to |
You are the man, @Shahaed! Thanks this really resolves the issue. |
Environment data
"python.jediEnabled"
set to; more info How to update the language server to the latest stable version #3977): Language ServerExpected behaviour
Up until last update to vscode (I can't recall what was the previous version), then with vscode-python update along vscode update, I lost lint on change feature, which has been running fine for long time for me according to #408.
Actual behaviour
No linting except on save.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)The text was updated successfully, but these errors were encountered: