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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Sun, 11 Feb 2024 09:04:08 +0000
with message-id <E1rZ5ku-005oqD-RT@fasolo.debian.org>
and subject line Bug#1063491: fixed in python-jedi 0.19.1+ds1-1
has caused the Debian Bug report #1063491,
regarding python3-jedi: unvendoring python3-typeshed breaks other packages
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


--
1063491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063491
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 8 Feb 2024 21:35:38 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-117.2 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,
DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,SPF_HELO_NONE,SPF_NONE,
T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,
USER_IN_DKIM_WHITELIST,XMAILER_REPORTBUG autolearn=ham
autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 13; hammy, 144; neutral, 47; spammy,
0. spammytokens: hammytokens:0.000-+--python3,
0.000-+--Hx-spam-relays-external:sk:stravin, 0.000-+--H*RT:sk:stravin,
0.000-+--Hx-spam-relays-external:311, 0.000-+--H*RT:311
Return-path: <jdg@debian.org>
Received: from st