-
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
The latest v2023.18.0 is causing the linter option to run bandit which is not available and auto-enabling the default (.venv) even when not requested. #22163
Comments
@iamibi Can you share your user and workspace settings? |
Same happens to me, but with |
Same for me (for |
I was able to figure out the issue. So, I was using WSL and even though my workspace settings never mentioned anything about |
Thanks @iamibi – I use a Mac, so the WSL solution doesn't apply to me unfortunately. Any clues on how you found the offending setting file? Edit: Found the solution, at least for me. Here are the steps:
@maltsev I suspect it might fix it for you as well! |
Weird that this issue started popping up after the recent update. Something was fixed (un)knowingly. Maybe the team can say it "It's not a bug, it's a feature :P" |
The default for most of these is false: Lines 682 to 683 in e7dfef8
Lines 783 to 784 in e7dfef8
It should not trigger these linters unless explicitly set to |
Thanks! Actually, that was the first thing I tried :-) It did solve the issue for some workspaces but not for other ones. So in the end, I just installed the new flake8 plugin. |
This is now fixed in pre-release |
I updated the python extension to the latest and I started receiving errors that the extension was trying to run
bandit
linter (i never configured it). Additionally, not some random.venv
is activated on the vscode terminal (again, not my configuration). I have to manually set the bash source to.bashrc
and then activate my custom virtual environment (separate from the one that was activated by the extension).Rolling back the python extension to
v2023.16.0
resolved this issue for me.The text was updated successfully, but these errors were encountered: