Hello, I am an upstream maintainer and ask just because I want to learn.
It was a similar case before the Debian 12 release introducing Python 3.12 near to the freeze. Why are fresh Python releases introduced so early and near to the next Debian release?
This is not how I do experience Debian at all. This is not "rock solid". Python 3.13 is very fresh, no one needs it yet. I see no problem introducing it with Debian 14 in 2027.
For my project it does not matter directly. I do support 3.13. But this process does bind a lot of resources on Debian which could be used more productive into other problems.
Who decide which Python version is introduced in Debian? Isn't there a council for heavy decisions like this?
Regards, Christian Buhtz Am 13.11.2024 11:04 schrieb PICCA Frederic-Emmanuel:
do we know how long we will have to fix all the FTBFS and autopkgtest before the freeze ? I am a bit worrying for the scientific stack , will we have enough time to work with our upstream in order to fix all these FTBFS. In the scientific stack, things are going slowly.... We are not 100% of our time dedicated to Debian work... so I hope that it will not ruine the effort of the trixie cycle for scientific softwares. moving to Python 3.12 was not that simple... Cheers Frédéric
