Adapt to the last Jedi

[sunlin7]

Hi,
Error happend with fresh installed python-language-server.
After check the error message, it cause by incompatable dependency that python-language-server depend on 0.14<=JEDI<0.16, while the pip actually install the last JEDI (0.16.0) when install pyls.

The workaround is change the setup.py to depend on JEDI 0.15.2.

Is there any plan to cachup with last JEDI (0.16.*)?

Thanks

The JEDI releases are:
https://github.com/davidhalter/jedi/releases

[wy-z]

ERROR: python-language-server 0.31.8 has requirement jedi<0.16,>=0.14.1, but you'll have jedi 0.16.0 which is incompatible.
ERROR: python-language-server 0.31.8 has requirement ujson<=1.35; platform_system != "Windows", but you'll have ujson 2.0.0 which is incompatible.
ERROR: python-jsonrpc-server 0.3.4 has requirement ujson<=1.35; platform_system != "Windows", but you'll have ujson 2.0.0 which is incompatible.

[hrehfeld]

Status? pyls is broken on archlinux.

[ccordoba12]

It's not our problem that upstream maintainers are not respecting our declared dependencies.

So instead of complaining here (because we're doing our job correctly), please inform this problem to your Linux distro.

[hrehfeld]

Sorry, but I didn't complain. I asked about the status of this issue and provided (hopefully valuable) info about problems larger parts of your userbase might run into. Next time, it'd be advisable to check the bugtracker of the distro you complain about before scolding your users.

What's the status on this issue?

PS. arch workaround by simply downgrading jedi: pacman -U /var/cache/pacman/pkg/python-jedi-0.15.*-any.pkg.tar.xz

[ccordoba12]

What's the status on this issue?

Let me put it this way then: there's nothing for us to solve yet (and as I said before, it's not our fault that the PyLS is broken in Arch) because we're are declaring our dependency on Jedi correctly:

python-language-server/setup.py

Line 38 in 143d993

'jedi>=0.14.1,<0.16',

So if that constraint is not respected by Arch maintainers, there's nothing we really need to do about it here, and you have to inform them that they introduced the breakage by not respecting it.

Next time, it'd be advisable to check the bugtracker of the distro you complain about before scolding your users.

I'm sorry but you're the Arch user and the one with this problem. So it's up to you to find out if the problem is reported in your distro or not. And also to find the solution you posted above.

---

Finally, and going directly to the point, we'll try to update to Jedi 0.16 in the coming months, but there's no firm plan to do it yet.

[sunlin7]

@ccordoba12 Thank you for your information, there're workarounds for pip/pacman.
Looking forward pyls migrating to the last jedi.

[stonebig]

yesterday (march 20th) python-vscode extension moved to jedi-0.16 .0 https://devblogs.microsoft.com/python/python-in-visual-studio-code-march-2020-release/ , so I suppose python-langage-server will have to move soon, and couldn't move before

... also not a field of roses on Windows / Python-3.8 microsoft/vscode-python#10357

[hrehfeld]

Thanks for the status update and taking care of this!

I'm sorry but you're the Arch user and the one with this problem. So it's up to you to find out if the problem is reported in your distro or not. And also to find the solution you posted above.

That's what I did before posting, but I was interested on the status of migrating to jedi 0.16 nonetheless.

[ccordoba12]

@stonebig, thanks for the info but the VSCode extension stopped using this project a long time ago.

@hrehfeld, thanks for understanding and sorry if I was too blunt yesterday with my first answer. I was under a lot of stress.

[stonebig]

to the best of my experiment, there is no apparent issue for basic Spyder-4.1.1 with Jedi-0.16.0.

[ccordoba12]

That doesn't mean the test suite here and ours are passing.