Jedi is stuck on loading after you preview the function document with the shortcut key

[CatNofishing]

Version: 1.43.2 (system setup)
Commit: 0ba0ca52957102ca3527cf479571617f0de6ed50
Date: 2020-03-24T07:38:38.248Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

#Bug ： Jedi - intelisense

Some function documents that are not recognized by Jedi will cause Jedi to be stuck in the loading state for a long time. expecially for 'pyi' file.

Description：

For example , If you write the code, “from PyQt5.QtWidgets import QApplication” ，and through the shortcut key to view the function document of QApplication, Jedi will be stuck in the loading state. Of course, this problem is not limited to pyqt5 module. Some functions in other modules that are not recognized by Jedi will cause the same problem.

This really affects the programming experience. I hope you can fix it. Thank you.

Here is a GIF demo file：

[kimadeline]

Hi @1470391328, thank you for reaching out.

When you say

Some functions in other modules that are not recognized by Jedi will cause the same problem.

Are those modules your own code, or packages you installed? For your issue with pyqt5, how did you install it?

Could you provide a sample repo I could use to replicate your issue? Can you also try using the Microsoft Python Language Server (by setting python.jediEnabled to false) and see if the issue persists?

Thanks!

[CatNofishing]

Thank you for your reply! I use Anaconda's Python environment, and all the packages come from anaconda. Microsoft language server works very well, and there is no similar problem. But because Microsoft language server doesn't support 'PYI' files and the CPU utilization is sometimes too high, I don't use Microsoft language server. For Jedi, the intelligent prompt seems to be stuck on pyqt5 package if you jump to its' PYI 'function document through the shortcut key

[kimadeline]

Sorry for the late reply @1470391328!

An interesting behaviour happened when I was trying to replicate your issue: I could jump to PyQt5 or QApplication in the beginning, but if I moved the cursor or the scrollbar in QtWidgets.pyi file I would not be able to use the "jump to definition" shortcut anymore:

The jedi methods that allow us to jump to the definition work (since they work the first time), so there is something else going on there, either in VS Code or the extension.

Sadly I couldn't find a workaround at the moment (except for reloading the window and making sure that your settings also contain "python.languageServer": "Jedi", or using the Microsoft Language Server despite its CPU usage).

Can you try downgrading the extension to an earlier version (2020.2.64397 or 2020.1.58038) and see if the problem also appears?

Thanks!

[CatNofishing]

I have tried different versions of Python extension (2020.2.63990-2020.3.71659). All versions have similar problems. In 2020.2.63990, although the intellisense snippets will be stuck in the loading state when you jump to pyqt5 library file, the "jump to definition" can work normally.

[kimadeline]

Interesting 🤔 We updated the extension in 2020.3.69010 to use jedi 0.16.0, so the difference should be between 2020.2.64397 and 2020.3.69010, not 2020.2.63990.

Thank you for reporting your workaround to downgrade to 2020.2.63990, we'll have to investigate it further 🔍

[CatNofishing]

This is a interesting Bug 😁. It's like a deep water 💣，

[CatNofishing]

@brettcannon @kimadeline
This issue is still exiting in latest version. Can you fix this bug?

[kimadeline]

Sorry we don't give ETAs. It is not forgotten, but not at the priority at the moment.

[CatNofishing]

😥

[luabud]

Can you try our insiders build and see if this is fixed? thanks!

[karrtikr]

I can verify I still see this issue with Jedi. But this is not a issue for me with Pylance. Please try setting python.languageServer to Pylance to fix the issue, thanks!

If you try out Pylance and this issue persists, you can open an issue on the pylance-release repo.

[karrtikr]

Closing in favor of #10895 (comment)