Skip to content
This repository has been archived by the owner on Dec 24, 2020. It is now read-only.

RuntimeError related to Jedi version being too old #236

Open
EdmundsEcho opened this issue Jun 23, 2020 · 7 comments
Open

RuntimeError related to Jedi version being too old #236

EdmundsEcho opened this issue Jun 23, 2020 · 7 comments

Comments

@EdmundsEcho
Copy link

Result from CocInfo

versions

vim version: NVIM v0.4.3
node version: v14.3.0
coc.nvim version: 0.0.78-263ec93b2c
coc.nvim directory: /Users/edmund/.config/nvim/bundle/coc.nvim
term: iTerm.app
platform: darwin

Output channel: prettier

Output channel: Python

Starting Jedi Python language engine.
##########Linting Output - pylint##########


Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)

##########Linting Output - pylint##########


Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)

Describe the bug

Calling the jump to definition function triggers a Runtime Error

[coc.nvim] Jedi error: Traceback (most recent call last):
[coc.nvim] Jedi error:     raise RuntimeError("Jedi version %s too old, requires >= 0.17.0" % (jedi.__v
ersion__))
[coc.nvim]: Error on notification "jumpDefinition": getDefinition timeout after 5s
Press ENTER or type command to continue

To troubleshoot, I updated the extension, plugin and plugin-manager.
... to no avail.

I then tried to uninstall the coc-python extension and received the following error

[coc.nvim] Uninstall failed: item.dispose is not a function

I tried to use the vim mini configuration, but it did not seem load the coc extension despite pointing it to the directory printed in the CocInfo output.

From what I have deduced, I'm not sure the Jedi script is being updated with the coc-python extension. Is that possible? Is there a way to manually update Jedi? (despite the docs that say not to update directly). Is there something wrong with Jedi?

Update

Everything works as expected when I replace Jedi with the MS language server with the setting "python.jediEnabled": false, in my config.

- E

@chemzqm chemzqm transferred this issue from neoclide/coc.nvim Jun 24, 2020
@stimw
Copy link

stimw commented Jun 25, 2020

same problem, I‘ve updated jedi,but still “Jedi version %s too old“

@1ak31sha
Copy link

same problem here

@g-i-o-r-g-i-o
Copy link

same on WSL 1 and ubuntu 8.2

@j-bucholtz
Copy link

Same issue on Pop!_OS 20.04.

@g-i-o-r-g-i-o
Copy link

g-i-o-r-g-i-o commented Sep 7, 2020 via email

@SinclairHudson
Copy link

Same issue on ubuntu 20.04... Is this a problem with Jedi or coc?

@Himon-SYNCRAFT
Copy link

If you are using virtual environment run "pip freeze" command and check jedi version in your project. It might differ from version you have installed globally.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants