When running a program that requires jedi, this error occurs: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 666, in _build_master ws.require(__requires__) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 984, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 875, in resolve raise VersionConflict(dist, req).with_context(dependent_req) pkg_resources.ContextualVersionConflict: (parso 0.1.1 (/usr/lib64/python3.6/site-packages), Requirement.parse('parso>=0.2.0'), {'jedi'}) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python-exec/python3.6/ptpython", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 3147, in <module> @_call_aside File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 3131, in _call_aside f(*args, **kwargs) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 3160, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 668, in _build_master return cls._build_from_requirements(__requires__) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 681, in _build_from_requirements dists = ws.resolve(reqs, Environment()) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 870, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'parso>=0.2.0' distribution was not found and is required by jedi The dependency on dev-python/parso should be updated to require >=0.2.0.
Additionally I'm rather tired of running behind jedi, fixing a consumer to work with any jedi bump, with no coordination done, so things are just broken for a while. 0.10 broke API and a consumer stopped working. 0.11 broke API and a consumer stopped working. I have no reason to think 0.12 won't break things yet again :( Please consider trying to coordinate bumps and stabilizations with potential consumers, so that they actually work with the same keyword visibility versions.. (Note that the consumer I talked about is gnome-builder, which doesn't have dev-python/jedi in RDEPEND as it'd be a huge set of pure runtime optional deps behind USE flags, which is not nice; it does however mention it in elog, so grep would see it)
Can confirm this bug, and have just worked on getting a parso-0.3.1 package built as a note jedi-0.12.1 forces a dependency on >=parso-0.3
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cd5174b37c3dddd45adfa70312520210987ca785 commit cd5174b37c3dddd45adfa70312520210987ca785 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2018-08-30 16:33:49 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2018-08-30 17:24:54 +0000 dev-python/jedi: Bump to 0.12.1 Bump to 0.12.1. Includes fixed test suite and dependencies. Closes: https://bugs.gentoo.org/664352 Closes: https://bugs.gentoo.org/656382 dev-python/jedi/Manifest | 1 + dev-python/jedi/jedi-0.12.1.ebuild | 62 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 63 insertions(+)
