You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a list of all the rules pylint runs that requires file traversal, like cyclic-imports?
If not, is there a way to analyze the codebase to get that information, even if not simple? (For
instance, is there a known list of helper functions that traverse files that I can use to find all
checkers that call it?)
Essentially, I'm trying to see if I can run pylint in two ways: run pylint on only changed files
for a "quick" check, and run specifically the traversal-dependent rules on the entire repo.
Similarly, a list of rules that are known to be "heavy" (slower/requiring more CPU or memory than
average) would be very useful for the same reason.
Thank you for opening the issue. No such option or list exist but it would indeed be useful. (Because other linter like flake8 and ruff only analyses file per file, many users are probably interested in only running pylint's multifile checks.)
Question
Is there a list of all the rules pylint runs that requires file traversal, like
cyclic-imports
?If not, is there a way to analyze the codebase to get that information, even if not simple? (For
instance, is there a known list of helper functions that traverse files that I can use to find all
checkers that call it?)
Essentially, I'm trying to see if I can run pylint in two ways: run pylint on only changed files
for a "quick" check, and run specifically the traversal-dependent rules on the entire repo.
Similarly, a list of rules that are known to be "heavy" (slower/requiring more CPU or memory than
average) would be very useful for the same reason.
Documentation for future user
For documentation, having annotations in https://pylint.pycqa.org/en/latest/user_guide/checkers/features.html
would be the ideal place.
This would also feature as a handy list of "issues you might miss if you don't run pylint comprehensively".
Additional context
No response
The text was updated successfully, but these errors were encountered: