Python autocompletion issues

[CPapadim]

I set up Theia and installed pyls and associated packages. Everything is working great except for a couple of issues with autcomplete.

Issue 1 - When importing modules
When I do this:
from matplotlib import pyplot. autocomplete won't read deeper into pyplot and won't show any module functions when the suggestion box pops up. For example, pyplot.Axes is a thing, but it won't show up as a suggestion. This is true even if I start typing pyplot.A ... with only suggestions being taken from the current file.

If I do this though:

from matplotlib.pyplot import it will suggest things (including the Axes() class) that are inside pyplot, so in that case it's reading them.

Case 2 - in the code itself after modules like pyplot is imported, doing this returns suggestions

pyplot. will show suggestions automatically.

but pyplot.Axes. will not show suggestions E.g. Axes.fill is a thing but won't show up, and the only suggestions are things taken from the current file. However, if I type pyplot.Axes.f then the fill() function shows up as a suggestion, so if I start typing the first letter, then the suggestion seems to pop up correctly, which is different behavior from the case when importing modules.

pyplot.Axes. will not show suggestions unless I type a letter first. So if I type f after the period, then functions with f like fill will show up.

On the other hand, this works:

pyplot.cm.cbook.delete_masked_points() to suggest completions along the entire path (so after pyplot, after cm, and after cbook), at each dot, so it's not necessarily an issue of the number of levels.

[svenefftinge]

We are using the pyls. Did you check another IDE that uses pyls (e.g. VS Code)?
Does it have the same issues?

[CPapadim]

Hmm that's a good question, I don't think I have an easy way to do that since I'm on windows and running theia in a linux docker container. I can maybe give installing monaco on the docker image a shot to verify if this behavior is due to pyls or theia.

[svenefftinge]

No, I mean could you install VS Code locally together with the python extension that uses pyls (not the new ms one) and see if your issues can be reproduced?

[vince-fugnitto]

Closing due to inactivity and #6933.
Issues regarding Python support should now be filed against the appropriate VS Code extension if the problem persists.