-
Notifications
You must be signed in to change notification settings - Fork 285
Pip install fails with ujson error #857
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
When I use |
Following command resolve this problem in my case. |
Uhm this should fail when the server start, as one component (pyls or the jsonrpc-server) will complain that the incorrect version of ujson is installed. |
This will be fixed when PR #842 is merged and a new version is released. |
This comment has been minimized.
This comment has been minimized.
@GNSubrahmanyam this is the current bug, that ujson 1.35 is installed by requirements of pyls, but jsonrpc-server requires >=3.0. The patch from #842 fix this issue, installing ujson >=3.0 in pyls if Python 3 is used. We need to wait for the new release, or manually edit the METADATA in site-packages to fix the current mismatch |
This comment has been minimized.
This comment has been minimized.
I use pip>=20.2 and It includes new feature of dependency resolver, but it is not included by default. The command |
Upgrading to python-language-server version 0.35.0 (https://github.com/palantir/python-language-server/releases/tag/0.35.0) solved the issue for us |
Uh oh!
There was an error while loading. Please reload this page.
Default pip installation fails with error for wrong
ujson
version.pip install python-language-server
Error:
Since the dependency lib
python-jsonrpc-server
was updated to v0.4 the updated ujson version leads to an incompatible installation with current settings ujson 1.35 in pyls.Latest version of python-jsonrpc-server: https://pypi.org/project/python-jsonrpc-server/
Depending pr: https://github.com/palantir/python-jsonrpc-server/pull/44/files
Workaround: use
python_jsonrpc_server<0.4
Possible solutions:
ujson
tooMaybe blocked by #808
Quick and easy fix by #859
The text was updated successfully, but these errors were encountered: