Jake Bailey

FWIW the new LS we released today has full typing support (and a new typeshed): https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-rich-language-support-for-python-in-visual-studio-code/

This is probably going to require some hefty changes to the TypeAnnotation stuff, since right now if a constant string is seen, we assume that it's supposed to be another...

FWIW the new LS we released today has full typing support: https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-rich-language-support-for-python-in-visual-studio-code/

This is an old issue, but you'd be interested in checking out Pylance, which uses Pyright for type checking. Announcement here: https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-rich-language-support-for-python-in-visual-studio-code/

Your output lists a slew of extra paths. Is there a file named "numpy.py" or similar in any of those paths, such that the module is resolving to the wrong...

Hm, is there a file named "numpy" in the workspace (`/home/user/PolloPatches`)?

One method is to kill the LS process; the VS Code client will restart the process up to 5 times. Another is to switch interpreter and go back again, which...

I'm not entirely certain how to debug this without the actual workspace. `numpy` aliasing is the main thing to check, and switching to a fresh repo but with the same...

A folder named `numpy` may also do it, but I'm assuming you're also checking for that. Maybe the output of `tree` to get the gist of how your code is...

Have you tried on 0.5.51 (which I believe is in our beta channel)? ``` "python.analysis.downloadChannel": "beta" ```