-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Emit a UserWarning
and crash pylint if run in parallel and with custom plugin
#7814
Conversation
So there are legitimate test cases to update so they don't run both in parallel and with plugins, good to know... if a maintainer ποΈ this PR and thinks it's good, I'll update the tests. |
Isn't the conclusion in the issue's discussion that we should crash ? |
pylint/lint/run.py
Outdated
"Running pylint in parallel with custom plugins is not currently supported.", | ||
UserWarning, | ||
) | ||
sys.exit(32) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm Ok I'm not super convinced anymore after realizing that if you run
pylint test.py --enable=all --enable-all-extensions
on any test.py module raises this warning now...
which is prob because of --enable-all-extensions
.
Maybe the code needs to be that config.jobs can be either 0
or anything >1? that would make more sense...
Yes, plus a warning if I understood correctly. I did that in the code but didn't properly say that in the title + PR description, will update it.
|
UserWarning
if pylint is run in parallel and with custom pluginUserWarning
and crash pylint if run in parallel and with custom plugin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #3232 (comment)
4e0afcb
to
1ce3628
Compare
Pull Request Test Coverage Report for Build 3568899284
π - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems 4 lines are not covered, would you mind adding a configuration functional tests, please ? (https://pylint.pycqa.org/en/latest/development_guide/contributor_guide/tests/writing_test.html#functional-tests-for-configurations)
This comment has been minimized.
This comment has been minimized.
d2a16fe
to
9a3fb56
Compare
This comment has been minimized.
This comment has been minimized.
9a3fb56
to
81a2a48
Compare
This comment has been minimized.
This comment has been minimized.
81a2a48
to
1c98865
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π
Co-authored-by: Pierre Sassoulas <[email protected]>
π€ According to the primer, this change has no effect on the checked open source code. π€π This comment was generated for commit 8e623c4 |
This should be ready to merge |
Let's wait for another maintainer review for this one. |
Closing since issue requirements have changed. |
Type of Changes
Description
Closes #3232
As issue an as pylint docs, users should not run pylint in parallel AND with custom plugins.
Looks like this now:
and pylint then stops execution