Package: python3-jedi Version: 0.17.2-2 Severity: important X-Debbugs-Cc: david.m.co...@gmail.com
Dear Maintainer, Version 0.17.2 of jedi is not compatible with 0.8.1 of parso (the current version in unstable). It requires a 0.7.x version of parso. The upcoming 0.18 release of jedi should be compatible with parso 0.8.x. In particular, parso 0.8 switched to using pathlib.Path for path names, instead of strings, so anything that ends up touching a path name in jedi may break. I've found that completion in IPython is completely broken, for instance. Here's some code (from the Jedi manual) that breaks: >>> import jedi >>> code = '''import json; json.l''' >>> script = jedi.Script(code, path='example.py') >>> script <Script: 'example.py' <SameEnvironment: 3.9.1 in /usr>> >>> completions = script.complete(1, 19) Traceback (most recent call last): File "<stdin>", line 1, in <module> ... File "/usr/lib/python3/dist-packages/jedi/inference/value/module.py", line 159, in is_stub if self._path is not None and self._path.endswith('.pyi'): AttributeError: 'PosixPath' object has no attribute 'endswith' (However, if the 'path' argument to Script is dropped, Jedi will compute the expected result.) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'unstable-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.9 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-jedi depends on: ii python3 3.9.0-4 ii python3-parso 0.8.1-1 python3-jedi recommends no packages. python3-jedi suggests no packages. -- no debconf information