Kernel-based autocomplete doesn't work for editors with an attached kernel

[sntgluca]

Description

Hi, following up with #586, I noticed that disabling LSP completion removes autocompletion in the editor even if a console is attached. Without the jupyter-lsp package, it's possible to attach a console to the editor to get kernel-base completion for it. Although it's not the best user experience, it gets the job done. I'd expect this feature to be maintained if

"disableCompletionsFrom": ["LSP"]

is used.

Reproduce

1. Disable LSP autocomplete in Advanced Settings -> Code Completion

{"disableCompletionsFrom": ["LSP"]}

2. Open a python file in the editor
3. Right-click -> Create Console for Editor
4. Type and try autocompleting any statement -> nothing happens.

Expected behavior

I'd expect autocomplete to work for editors with a kernel attached.

Version

Tested on JupyterLab 3.0.18 and juptyer-lsp 3.7

[timothymillar]

I have also run into this issue. Just for clarity "disableCompletionsFrom": ["LSP"] is not the cause of the issue but just makes the symptoms more obvious. With "disableCompletionsFrom": [] I still run into this issue if I attach a console to an external kernel that contains libraries not installed in the jupyterlab environment.

[flaport]

Has anyone found a solution for this? I find kernel based completions very useful in my exploratory notebooks. Ideally I would like to combine both the LSP completions and the kernel completions.

[krassowski]

@flaport it should work fine for notebooks. This issue is about enabling this for text files ("editors"). If it does not work for you please fill in a bug report template.