-
Notifications
You must be signed in to change notification settings - Fork 34
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
Automatic restart after library is installed #560
Comments
@ibobak Please provide logs from Output > Pylint. |
Logs before opening core.py:
logs after opening core py (just when I opened it, I got errors; pyspark is still not installed at this moment)
Now I am running pip install pyspark and opening logs after this installation finishes:
At this moment in core.py I still see errors (while I should NOT see them, because pyspark is installed). now I am closing core.py, re-opening it agan -
And it looks like the problem has gone. But here is where the problem is: as soon as I installed "pip install pyspark", those open editors which are using it, HAVE NO IDEA that their code is referencing an existing library, until I close them and re-open again. is is possible to automatically re-launch pylint after pip install is done? |
I got one more related bad behavior: here is the video https://youtu.be/fZo5GL1veLg |
This is the whole log which was got during this video |
@ibobak We don't plan on doing this automatically. Monitoring package installs and large folder trees can cause significant performance issues. You can use the I will leave this open, in case we have alternative ways to do this. |
@karthiknadig I would like to kindly ask you to watch this short video: https://youtu.be/fZo5GL1veLg I've shown how to reproduce the error: |
My point is this: the lines are either errorneous, or they are correct. But on the video I am showing that they are first not marked (=correct), but just after "go to declaration" and "back" they suddenly become errorneous. |
@ibobak The one in the video seems like a different problem. It seems like there is some kind of cacheing issue. Can you try using the latest pre-release version of the extension which has the latest pylint? |
Type: Bug
The missing module is already installed, however, in editor I still see "unable to import" message.
The package is 100% installed, I can navigate to that code. But pylint doesn't see this - this is the problem.
If it cannot automatically detect new packages, that would be good to have some "force rescan" command or something like that, because this is not obvious, really. In PyCharm such things were done totally automatically.
Extension version: 2023.10.1
VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:16:23.416Z)
OS version: Linux x64 6.4.6-060406-generic
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: