Package: python3-jedi Version: 0.19.1+ds-1 Severity: grave Unfortunately, just removing the vendored typeshed from this package causes other packages to break. I don't fully understand the mechanism, but jedi looks to load things from the vendored directory, and if it doesn't find them, things go horribly wrong. It's broken the spyder (autopkg)tests, and several others (see tracker.debian.org for details). To be sure that python3-jedi was the cause, I built a local version of python3-jedi 0.19.1 with the vendored typeshed still present, and the spyder tests work fine with this single change.
A reasonable (short-term?) fix is to reintroduce the vendored version of typeshed. This is much better than having a broken package. A horrible fix is to symlink all of the stubs from the python3-typeshed to the expected places in jedi/third_party/typeshed, but that seems like a lot of work. (One would have to get rid of typeshed/stdlib/2/ in the process, but I don't know if that will break things. Hopefully not!) Most of the stubs in python3-typeshed are not imported into jedi/third_party, only a few. But the directory layout is very different. A probably better fix would be to change the code in jedi to not look for the third_party/typeshed directory and to perhaps look in /usr/lib/python3/dist-packages/*-stubs instead (as python3-typeshed stores its stubs in multiple directories). But that's significantly more work and will be harder to test. Best wishes, Julian
