-
Notifications
You must be signed in to change notification settings - Fork 52
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
python.linting.ignorePatterns
setting is not used
#175
Comments
Oh interesting, I didn’t know about this setting. On the surface, I agree with you, though I’d like to see if / how other similar extensions handle them before committing. |
It looks like the other Python extensions don't respect this, but there's a recently-opened issue (microsoft/vscode-flake8#147) discussing it. |
There was some recent discussion in the pylance project about how this setting is meant for linters: microsoft/pylance-release#4100 Here's the same feature request for the pylint extension: microsoft/vscode-pylint#199 |
Imo this does seem like a nicer way to do it than to have configuration for each extension. I'm not familiar with how these extensions are built, but it seems like there are varying levels of support. Is the intention behind I also read about some other extensions utilizing (i think) the |
Ok, it looks like this setting is considered legacy, and they plan to deprecate it: microsoft/vscode-flake8#147 (comment). |
It would be really useful if the
python.linting.ignorePatterns
VS Code setting would be honoured by this extension. This would make it easy to for example exclude standard library modules from the analysis that would otherwise pollute the problem list if you ever jump to them.Of course you can configure exclude paths in
pyproject.toml
, but you would have to do that for each project individually, and in cases where you edit stand-alone scripts you wouldn't even have a project file.If both these VS Code patterns and excludes in the
pyproject.toml
are configured I would suggest using both. This means people can have their own excludes configured for a shared project, and if their normal excludes are undesirable for a specific project they can always set the patterns to a different value in their workspace settings.The text was updated successfully, but these errors were encountered: