Default Python version for trixie, how to deal with 3.13 transition ?
Hello
quoting an email from debian-devel
> Python:
> [...]
> I am also unhappy that no actual proposal for freeze dates are given at
> this point of time. This doesn't allow any useful planning for getting
> ready for the release with specific upstream versions. Talking here
> about the Python 3.13 migration, and the issues we had during the
> bookworm freeze. I had been asking about a later freeze for that, but
> looking back at emails, I don't see any feedback on that from the
> release team. So just based on personal and private conversations, we
> will go ahead with plan to ship trixie with Python 3.13 as the default,
> and assuming later freeze dates than we had for bookworm. But it would
> be nice if this communication could be more public for future releases.
In Debian Science we have lot's of Python modules/applications and it tooks
most of the trixie cycle to have these packages in testing with the current
Python 3.12 version.
I do not know if the migration to 3.13 will not kick out of testing a big
part of our team maintain Packages. I do not know either if we will have
enought time to work with upstreams in order to suppport Python 3.13 if it happens.
If enough packages are instrumented with autopkgtest, we could have a good view of the remaining work.
Do you know if a mass rebuild and execution of our autopkgtest have be done with Python3.13 ?
Fred
Reply to: