c.Completer.use_jedi instruction may be pointing to the wrong config file
See original GitHub issueWhat I am trying to do…
Speed up tab completion by telling IPython not to use Jedi
How I would like to learn how to do it…
Following the Readme
How the project might keep the docs accurate…
The readme says to modify c.Completer.use_jedi
in ipython_kernel_config.py
but I believe that this config setting is actually defined in ipython_config.py
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:24 (21 by maintainers)
Top Results From Across the Web
How to config 'Completer.use_jedi' to 'False' in Juypter ...
I launch my jupyterlab from docker and catch this problem. I solved like this:
Read more >How to enable Autocompletion in Jupyter Notebook application
Once you have enabled and run the %config Completer.use_jedi = False magic command, you can trigger the code autocompletion by pressing the tab ......
Read more >Language Server Protocol integration for Jupyter(Lab) - GitHub
You can configure the completer to not attempt to fetch the kernel completions if the kernel ... Completer.use_jedi = False in your ipython_config.py...
Read more >Jedi.el - Python auto-completion for Emacs - (to be determined)
To check that jedi:setup is called properly via python-mode-hook, run M-: jedi-mode RET in some Python file. It should return t . If...
Read more >Config file and command line options - The Jupyter Notebook
Config file and command line options . The notebook server can be run with a variety of command line arguments. A list...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@g6ai I just dropped the
<0.18.0
pin hereAh, yes! Sorry about not being clear/saying it in a misleading manner. The codebase of the pyls fork is compatible with Jedi 0.18 and even with Jedi master, but there is a pin that needs to be manually changed for pyls to work, so it will not work by installing it as-is but will require cloning -> changing the pin in setup.py ->
pip install .
. Plus the IPython version stuff. In any case 0.18 support is not production-ready yet, it’s more like “if you really want to check it out for benchmark, then it is possible”.