Created attachment 642410 [details] pyls traceback pyls fails to start, saying jedi needs parso>=0.7.0. However I can import jedi fine from python. I have the following package version installed: dev-python/python-language-server-0.32.0 dev-python/jedi-0.17.0 dev-python/parso-0.6.2 I attached the full traceback I get when I run pyls.
This is a bug in the jedi ebuild, not in the pyls ebuild. According to jedi upstream requirements.txt jedi should depend on parso>=0.7.0: https://github.com/davidhalter/jedi/blob/master/requirements.txt
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2a5c256d844538978770bb4197699c48c1c851b4 commit 2a5c256d844538978770bb4197699c48c1c851b4 Author: Florian Schmaus <flo@geekplace.eu> AuthorDate: 2020-06-02 08:48:43 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2020-07-17 04:18:20 +0000 dev-python/jedi: correct parso dependency Jedi 0.17.1 requires parso >= 0.7.0. Closes: https://bugs.gentoo.org/725984 Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Florian Schmaus <flo@geekplace.eu> Closes: https://github.com/gentoo/gentoo/pull/16048 Signed-off-by: Matt Turner <mattst88@gentoo.org> dev-python/jedi/{jedi-0.17.1.ebuild => jedi-0.17.1-r1.ebuild} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
