Provide configuration to disable this extension

[parched]

I would like my team to use the Ruff extension for flake8 linting instead of this one.
However, they will have this extension installed for other projects.
Currently, it is a manual step to disable this extension, but it would be much better if there was a setting for it.
Something similar to the formatting provider, perhaps, or just a setting to disable this extension.

[karthiknadig]

I highly recommend upvoting and leaving a comment on this issue: microsoft/vscode#40239

Thanks for the feature request! We are going to give the community time to provide 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[parched]

Ok, I'll put I comment there but I don't hold out much hope as that issue is over 5 years old.

Would you be open to me contributing this functionality?

[karthiknadig]

One thing is if we do it we will need to propagate it to two more extensions at least:
https://github.com/microsoft/vscode-pylint
https://github.com/microsoft/vscode-mypy

This is pycon week so we will discuss this for next iteration, and let you know our decision.

[luabud]

One way to work around this is to set up a Profile for your team with the Ruff extension, and not the Flake8 one: https://code.visualstudio.com/docs/editor/profiles

This way even if the Flake8 extension is installed in the default profile, it won't work/activate when working in the new profile.

For example, I have the Flake8 extension installed and enabled in my Default profile:

Then when I switch to my "Python Scripts" profile, I don't have it installed there:

[parched]

@karthiknadig Yes, I was thinking the same with respect to Pylint too as that's an extension some of the developers have installed for other projects.

Thanks @luabud I'll have a play with it. I would like developers to just be able to clone the repo and open it VS code and be ready to go.

[parched]

I tried the profile, but it doesn't look like it'll work, because it turns off all the user's other extensions. E.g, the Vim extension I use is project agnostic.

[luabud]

@isidorn -- do you have a suggestion for this? We could implement a disable setting for each of our linting extensions, but I'm pretty sure there is a more elegant solution in place already that I'm just missing 🤔

[isidorn]

The real solution is the one @karthiknadig already linked microsoft/vscode#40239
"Workaround" is to use profiles.
"Another workaround" - @parched create your own extension. The only thing your extension does it disable the extensions you want disabled. Then you add your extension as part of the workspace extension recommendations and you are good.

I do not think a disable setting for each linting extension is the way to go.
This sounds like a VS Code problem. I suggest to close this as a duplicate of some VS Code issue and I think we will tackle this some time in the future.