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
this is the same as we did for the Python 3.12 transition. Please note that we don't enable any of the experimental features in Python 3.12 (no GIL, JIT compilation), so assuming there are currently no other RC
issues in your packages, there should plenty of time to fix any 3.13 related issues.
the plenty of time is not only my time or Debian time but also upstream time.
This was discussed at the Python BoF at DebConf in ROK earlier this
year.
This was discussed at the Python BoF at DebConf in ROK earlier this
year.
OK, nice to know that there was a discussion before. Did I missed the announcement of the results of this discussion in this mailing list?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 493 |
Nodes: | 16 (2 / 14) |
Uptime: | 01:29:33 |
Calls: | 9,707 |
Calls today: | 2 |
Files: | 13,740 |
Messages: | 6,180,644 |