Bug#987013: Bug#996584: (some kind of) transition: add python3.10 as a supported python3 version
On Tue, Nov 16, 2021 at 02:23:36PM +0100, Matthias Klose wrote:
> I'm planning to upload python3-defaults later tonight, adding 3.10 as a
> supported Python version. Packages are able to migrate on their own, there are
> no blockages introduced on other transitions.
>
> We have most packages ready to build for 3.10, and around 70 leaf packages still
> needing some work. Otoh, we can much better work on these if reverse
> dependencies are already built for 3.10 in the archive. The tracker used is
>...
I think the backwards incompatible change to the dbm extension[1] has to
be reverted until after a release where someone has migrated the data of
all packages using Berkeley DB.
Most broken packages are likely not even among the ones that need
rebuilding, they would just be just broken and Python should not
make it harder to fix them.
If Berkeley DB removal should be done in trixie, someone will have to
analyze and implement solutions for data migrations as part of #987013
in bookworm. Ecosystem maintainers unilaterally dropping support would
only make it a lot harder to implement solutions.
How should a package like apt-listchanges migrate its database if the
existing reader code is no longer functional due to this change in Python?
That's not impossible, but might make things a lot harder.
AFAIK even Python 2.7 will still be shipped in bookworm, so let's not
make life harder for other people by hurrying too much with Berkeley DB.
> Matthias
cu
Adrian
[1] https://tracker.debian.org/news/1240462/accepted-python310-3100b1-2-source-into-experimental/
Reply to: