python-jedi fails to build with Python 3.10.0a2.
________________________ test_find_system_environments _________________________
envs = list(find_system_environments())
> assert len(envs)
E assert 0
E + where 0 = len()
______________________ test_completion_param_annotations _______________________
# Need to define this function not directly in Python. Otherwise Jedi is too
# clever and uses the Python code instead of the signature object.
code = 'def foo(a: 1, b: str, c: int = 1.0) -> bytes: pass'
script = jedi.Interpreter('foo', [locals()])
c, = script.complete()
sig, = c.get_signatures()
a, b, c = sig.params
assert a.infer() == 
> assert [d.name for d in b.infer()] == ['str']
E AssertionError: assert  == ['str']
E Right contains one more item: 'str'
E Use -v to get the full diff
__________________ test_compiled_signature_annotation_string ___________________
def func(x: typing.Type, y: typing.Union[typing.Type, int]):
func.__name__ = 'not_func'
s, = jedi.Interpreter('func()', [locals()]).get_signatures(1, 5)
> assert s.params.description == 'param x: Type'
E assert "param x: 'typing.Type'" == 'param x: Type'
E - param x: Type
E + param x: 'typing.Type'
===== 3 failed, 1451 passed, 20 skipped, 2 deselected, 5 xfailed in 42.38s =====
I understand the third failure: typing names/repor have been changed in Python 3.10.
For the first two failures, I have no clue.
For the build logs, see:
For all our attempts to build python-jedi with Python 3.10, see:
Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.10:
Let us know here if you have any questions.
Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
Latest upstream commit behaves the same. Bumping the severity here, an entire stack ipython stack depends on it.
Petr, could you please take this upstream?
Upstream issue created: https://github.com/davidhalter/jedi/issues/1732
Unfortunately, it seems that the fix will be much more complex than just adapting tests to new outputs.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.