> 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. I just wanted to express my concern because we rely at work on the scientific stack. So we try hard to maintain our packages in testing, and it it always a deception to see them (part of) expelled from testing due to an FTBFS with a new Python or a failing autopkgtest. amicalement, Fred
