Skip to content
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

Checking the configuration in a dedicated script instead of at runtime #8413

Open
Pierre-Sassoulas opened this issue Mar 9, 2023 · 1 comment
Labels
Enhancement ✨ Improvement to a component Minor 💅 Polishing pylint is always nice Needs specification 🔐 Accepted as a potential improvement, and needs to specify edge cases, message names, etc. performance

Comments

@Pierre-Sassoulas
Copy link
Member

Current problem

We're doing some "complicated" check all the time for example here: #8411

But it could be done once in a dedicated script instead.

Desired solution

No check at runtime but a possibility to validate the configuration. Maybe a better validation of the configuration. Or maybe not, this is not what is taking most of the time in pylint and maybe this will make the user experience worst for almost no benefit.

Additional context

#8411

@Pierre-Sassoulas Pierre-Sassoulas added Enhancement ✨ Improvement to a component Minor 💅 Polishing pylint is always nice performance Needs specification 🔐 Accepted as a potential improvement, and needs to specify edge cases, message names, etc. labels Mar 9, 2023
@Pierre-Sassoulas Pierre-Sassoulas added this to the 3.1.0 milestone Mar 9, 2023
@DanielNoord
Copy link
Collaborator

THis should probably just be part of pylint-config

@Pierre-Sassoulas Pierre-Sassoulas removed this from the 3.1.0 milestone Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement ✨ Improvement to a component Minor 💅 Polishing pylint is always nice Needs specification 🔐 Accepted as a potential improvement, and needs to specify edge cases, message names, etc. performance
Projects
None yet
Development

No branches or pull requests

2 participants