Re: Python 3.11 for bookworm?
On Sun, Dec 18, 2022 at 06:02:58PM +0000, Julian Gilbey wrote:
> On Thu, Dec 15, 2022 at 04:10:05PM +0100, Thomas Goirand wrote:
> > On 12/13/22 13:34, Julian Gilbey wrote:
> > > If Python 3.11 is the default, then it is highly likely that Spyder
> > > will not be included: debugpy, which is a dependency of Spyder and
> > > python3-ipykernel (and lots of things that depend on that) seems to
> > > require major work upstream to make it fully compatible with Python
> > > 3.11. This is work in progress, but I don't know whether it will be
> > > ready in time for the freeze. At the moment, I have worked around
> > > this problem by just skipping the failing tests, but that is far from
> > > an ideal solution.
> >
> > It's probably ok if it's a *TEMPORARY* solution until upstream fixes
> > everything in time for the release (which is months after the freeze). The
> > question is: do you believe this may happen for let's say next March?
>
> The truth is that I don't know. Upstream is very good, but the Python
> 3.11 internal changes are very significant, and debugpy (along with
> pydevd, which is part of debugpy) are deeply affected by this, as they
> work at the level of Python's internals. So I don't know how long it
> will take them to make the required changes (and it's far beyond my
> capability or capacity to do myself). I can hope they'll do it in
> time for the freeze, but I wouldn't like to place a bet on it.
Quick update: with the updating of python3-bytecode from 0.13 to 0.14
in unstable/testing, which allows it to handle Python 3.11, something
has changed and now pydevd doesn't even pass the tests on Python
3.10. The python3-bytecode underwent a major restructuring, so it is
entirely possible that something has changed that wasn't part of the
advertised API or something like that. But that's for upstream pydevd
developers to deal with.
One possibility is that we revert to the situation in bullseye if
pydevd is not ready in time for the freeze. Bullseye didn't have
bytecode/pydevd/debugpy, and it meant that debugging was limited in
Spyder: we remove python3-debugpy from the dependencies of
python3-ipykernel and then the rest of the dependency chain will be
OK. It's certainly not an ideal solution, but it may be the best we
can do if we're sticking with Python 3.11. It may actually be worth
doing that at this point so that Spyder can stay in testing for the
time being, even though pydevd and debugpy won't.
Best wishes,
Julian
Reply to: