[Bug 2153262] [NEW] SRU: backport Python 3.14.5 to 26.04 LTS

[Matthias Klose]

Public bug reported:

please let's backport Python 3.14.5 to 26.04 LTS. The main reason for
that backport is the reversion of the  incremental garbage collector in
in both 3.14 and 3.15 to the more conservative garbage collector used in
3.13 and before. See

https://discuss.python.org/t/reverting-the-incremental-gc-in-
python-3-14-and-3-15/107014

We did backports of minor Python 3.x.y release also in the past, having
as backport criterium

 - builds on all architectures
 - doesn't fail tests on any architecture (can't test on riscv64)
 - passes autopkg tests
 - rebuild of main doesn't show any regressions
 - 3.14.5-1 has to migrate to the stonking release pocket first.

I'm proposing to do the same, (except for the last point) for the 3.14.5
backport (or if the SRU decision gets delayed, for 3.14.6), except for
the the test rebuild.

Avoiding the test rebuild because of the instability of the buildd
infrastructure, waiting for a more stable version, or if we have to use
the current unstable builders, but in this case, I'd like to combine
that test rebuild with the planned GCC backports for July/August, and
testing these updates together in one test rebuild.

** Affects: python3.14 (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "3.14.5 release notes"
   https://bugs.launchpad.net/bugs/2153262/+attachment/5971670/+files/NEWS

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python3.14 in Ubuntu.
https://bugs.launchpad.net/bugs/2153262

Title:
  SRU: backport Python 3.14.5 to 26.04 LTS

Status in python3.14 package in Ubuntu:
  New

Bug description:
  please let's backport Python 3.14.5 to 26.04 LTS. The main reason for
  that backport is the reversion of the  incremental garbage collector
  in in both 3.14 and 3.15 to the more conservative garbage collector
  used in 3.13 and before. See

  https://discuss.python.org/t/reverting-the-incremental-gc-in-
  python-3-14-and-3-15/107014

  We did backports of minor Python 3.x.y release also in the past,
  having as backport criterium

   - builds on all architectures
   - doesn't fail tests on any architecture (can't test on riscv64)
   - passes autopkg tests
   - rebuild of main doesn't show any regressions
   - 3.14.5-1 has to migrate to the stonking release pocket first.

  I'm proposing to do the same, (except for the last point) for the
  3.14.5 backport (or if the SRU decision gets delayed, for 3.14.6),
  except for the the test rebuild.

  Avoiding the test rebuild because of the instability of the buildd
  infrastructure, waiting for a more stable version, or if we have to
  use the current unstable builders, but in this case, I'd like to
  combine that test rebuild with the planned GCC backports for
  July/August, and testing these updates together in one test rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.14/+bug/2153262/+subscriptions