-
Notifications
You must be signed in to change notification settings - Fork 174
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
[BUG] Segmentation fault when running pylint via prospector and importing cartopy #403
Comments
I used a debugger to find out where the segmentation fault happens. It seems that pylint follows a different code path when it is being run on its own VS when it is being run under prospector. When prospector is used, an instance of Nevertheless, that line is not executed when using plain pylint, at least not for |
Thanks for the detailed investigation! Out of curiosity - does prospector also segfault if you run it only with pylint? ( |
@carlio yes it does. |
@pmav99 I just tried to reproduce this locally and it does not seem to happen for me, using the exact |
Never mind just managed to repro it! |
…caused a segfault with cartopy, and also prospector requires at least pylint 2.8 now so this old workaround is not needed
Ok, tracked the issue down. The fix will go out with the 1.7.1 release shortly. |
When using pylint on a module that imports
cartopy
, prospector throws a segmentation fault. Running pylint on its own finishes without problems:pyproject.toml
Requirements.txt:
The text was updated successfully, but these errors were encountered: