-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ImportError on collection of module in pylint 2.5.0 when using multiprocessing option #3524
Comments
Thanks for the report! This is a regression caused by 2.5.0 which most likely was a result of #3411. Going to investigate and provide a fix hopefully this week. In the meantime I suggest downgrading to 2.4.4 or using |
Already did the 2.4.4 downgrading ;-), thanks for the quick reply! |
I noticed that 2.5.0 also doesn't calculate the score in multiprocessing mode - could it be related to this bug? |
Pinning the version of pylint as it's causing failures in our build. Related issue: pylint-dev/pylint#3524
* fix warning about junit family while testing * pin pylint version due to bug pylint-dev/pylint#3524
PyLint 2.5 is affected by pylint-dev/pylint#3524
PyLint 2.5 is affected by pylint-dev/pylint#3524
Could it be that some docs need updating?
|
Pin pylint version to workaround pylint-dev/pylint#3524
* fixing the function * adding comments and explanation in docstrings * fixing the pylint in tox due to the multiprocessing error pylint-dev/pylint#3524
Is there anything one can do to help resolving this issue and/or raise its priority? It's a complete show stopper for us, and judging from the linked commits/issues for many other projects, too. The workaround of using -j1 is not an option when you already wait 8 minutes in the parallel case... 😞 |
@svenpanne if you do no need any of the features/fixes introduced with 2.5.0 you can just pin pylint to a version which is not 2.5.0. Basically in your requirements.txt or setup.py (or wherever you specify the dependencies) use "pylint!=2.5.0" instead of "pylint". Version 2.4.4 will be used. When a fix will come you can remove the version specification. |
The suggested -j1 fix doesn't solve the problem. |
This is exactly what we are doing at the moment, just like tons of other projects if one looks at the linked issues. We have quite a few suppressions caused by false positives, so I thought giving 2.5.0 a try might be a good idea, but obviously it's not... |
@svenpanne I understand your pain. For context, almost all the minor releases had some issues in the past and I usually recommend to wait until a couple of patch releases before jumping to a minor version of Pylint. Usually the minor version that is going to be released does not get a lot of testing from the community and some critical issues leak into the minor release when that happens. Regarding bumping the priority, this issue is one of my main concerns for a 2.5.1 or 2.5.2 release. But it's non trivial and I also have a day to day job, so please be a bit patient on that front. As soon as we have a fix, you'll see the notification here. If you do want to help, investigating the root cause or sending a patch is more than welcome and appreciated. |
Pin pylint version to workaround pylint-dev/pylint#3524
Pin pylint version to workaround pylint-dev/pylint#3524
Unfortunately pinning to 2.4 is no longer a universal solution now because Safety has now marked pylint <2.5.0 to be insecure: https://github.com/pyupio/safety-db/blob/master/data/insecure_full.json#L10823-L10833 |
Hey folks, this should be fixed in both |
Works for me! Thanks for the quick turnaround. |
@PCManticore I can reproduce this, if I add "asdf" in the spam.py file mentioned in the "steps to reproduce" and copy this 20 times (or whatever) with a different name each time:
The |
Please open a separate issue with reproduction steps as the original issue was solved and the root cause for your issue might be different. |
Version 2.5.0 introduced a bug with the multiprocessing option. This happens often enough that we should have pylint pinned and only upgrade when we choose to do it. See pylint-dev/pylint#3524
Version 2.5.0 introduced a bug with the multiprocessing option. This happens often enough that we should have pylint pinned and only upgrade when we choose to do it. See pylint-dev/pylint#3524
Version 2.5.0 introduced a bug with the multiprocessing option. This happens often enough that we should have pylint pinned and only upgrade when we choose to do it. See pylint-dev/pylint#3524
Version 2.5.0 introduced a bug with the multiprocessing option. This happens often enough that we should have pylint pinned and only upgrade when we choose to do it. See pylint-dev/pylint#3524
Version 2.5.0 introduced a bug with the multiprocessing option. This happens often enough that we should have pylint pinned and only upgrade when we choose to do it. See pylint-dev/pylint#3524
* Fixing the iter_connection with unique_node_ids * fixing the function * adding comments and explanation in docstrings * fixing the pylint in tox due to the multiprocessing error pylint-dev/pylint#3524 * Change node_id to node ID in doc
Steps to reproduce
Current behavior
ImportError
Expected behavior
no error (for example with pylint 2.4.4)
pylint --version output
The text was updated successfully, but these errors were encountered: