MNT: let pylint use every core it is given - #1163
Merged
Gui-FernandesBR merged 1 commit intoAug 14, 2026
Merged
Conversation
jobs=1 pins the run to one process. Measured on eight cores over rocketpy/, tests/ and docs/: 36.4s at jobs=1 against 14.0s at jobs=0, and the two produce the same messages, so the gate is unchanged and only the wait is shorter. 0 asks pylint to count the processors itself, which is what the comment above the setting already describes, and it caps the count on Windows on pylint's own side. Signed-off-by: thc1006 <84045975+thc1006@users.noreply.github.com>
Gui-FernandesBR
approved these changes
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull request type
Checklist
pylint rocketpy/ tests/ docs/) has passed locallyCurrent behavior
.pylintrcsetsjobs=1, so the lint runs in one process no matter what the machine has. The comment directly above it already describes0as the auto-detecting value, including the Windows cap, so the setting reads as a leftover rather than a decision.New behavior
jobs=0. Measured overrocketpy/,tests/anddocs/on eight cores:jobs=1jobs=0I diffed the two message sets rather than trusting the exit code, since some checkers behave differently when the files are split across processes. They are identical, so the gate is the same one and only the wait is shorter.
This reaches CI, the
Makefiletarget and a plain localpylintat once, because all three read this file rather than passing-j.Breaking change
Additional information
Windows is the usual worry with
-j. pylint caps the process count there itself, which is what the comment in the file says, and the linters workflow runs onubuntu-latestin any case.