vscode-jupyter: Autocomplete hangs the kernel for interactive window
Version: 2020.1.58038 (13 January 2020)
I have a dataframe with shape of (810103, 26). If I type code and run a cell from the editor, everything is fine. But it will be extremely slow if I run code from the interactive window directly such as df.head(), df.columns. I can even make a screenshot without shortcut😂
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 6
- Comments: 46 (29 by maintainers)
Some of the advice here seems to alleviate the problem: https://github.com/jupyter/notebook/issues/3224
I typed this in to the interactive window:
and now it responds immediately. At least with the csv you mentioned above.
Could you guys please take a look. This is so weird and really interrupt my workflow.
Why don’t we keep track of the pending completion requests & let users know that things are slowing down because of Jedi in the kernel & ask them to just turn this off.
Some (if not most, totally guessing here) users will want this, to get better completion. Feel its better to let them know when things are slowing down & what they can do.
Just like in VS Code core, they let users know what extension is chewing up CPU process & slowing VS Code down, then Users can optionally blitz that extension. Similarly users can opt into disabling jedi completely (we can just add that into a startup command if they click
yesand if they want they can go back and just remove that line from the settings.json startup commands)Finally had a chance to profile the IPython kernel. The autocomplete from typing is hanging the kernel and preventing the execution of a cell. We should be able to fix this by interrupting the kernel if it’s in the middle of autocompletion.
You should be able to put this in your startup commands:
I take that back. Only sometimes with 2019.11.50794.