Great, thanks for outlining the plan Oleg.

On 11/15/26 21:27, Sharlatan Hellseher wrote:
Hi Guix!

Thanks Andreas for the merge!

So what would be next

Smooth bootstrap for Next Python
Hugo may you re-send PR please

Yeah I will, but need to figure out the best way to prevent circular imports.  See also https://codeberg.org/guix/guix/issues/9250 and

Break link to Rust, Java, Haskell, and Julia
https://codeberg.org/guix/guix/issues/12463

Yes, that would be great.  We need LLVM-13 for the Rust bootstrap (at least on some platforms), and for that we need Python 3.12. Maybe we should even have a specific `python-3.12-bootstrap`, as well a free floating `python-bootstrap` (which initially also will be 3.12, but might become 3.13).

Having the separate bootstrap Python would also help with the Python transformation, as a current difficulty is to prevent the transformation from transforming exactly those python dependencies that would become this bootstrap one.

And step inside darkness after 3.12->3.13 flip?
https://codeberg.org/guix/guix/milestone/95864

I won't stop you and will fix any 'important' (by my definition) packages; but I'm probably not going to patch random (often bioinformatics) packages that break.

(It was fine to fix random packages when there were no automated tools that can do that; because if anyone needs to do that labor, it might as well be me; taking one for the team.  But now we have machines that can do such tasks, so there is no actual 'need' for anyone to do that endless labor, which changed my perspective in two ways.  One: if the authors of the packages don't care to update them, and their users don't care either, and we do not want to use the machines to do it for us, then I don't see the point in me doing it.  But more importantly, perspective change nr. two: those packages are not broken, and there is no need to fix them at all.  Guix should allow to let them live side by side in the same repository (but in different profiles) with newer packages.  Hence my work on the selecting-Python-through-transformations, as I see that as a stepping stone to a solution.)

I would prefer we do this in two steps: one python-team iteration to decouple the 3.12 bootstrap Python, and a second iteration to upgrade to 3.13, because I do not want the decoupling to be dependent on the 3.13 upgrade.

The decoupling should be a 'trivial' world rebuild, as it would not materially change anything now (since both Pythons would be the same).  So maybe we could even do that on another branch, like the generic world-rebuild.



Oleg

VCS: https://github.incerto.xyz/; https://git.sr.ht/~hellseher/
GPG: 9847 81DE 689C 21C2 6418 0867 76D7 27BF F62C D2B5

… наш разум - превосходная объяснительная машина которая способна найти смысл почти в чем угодно, истолковать любой феномен, но совершенно не в состоянии принять мысль о непредсказуемости.

On Sun, 15 Nov 2026, 18:16 Andreas Enge, <[email protected]> wrote:

    I have just merged the branch to master, thanks a lot to all who have
    made this a smooth transition!

    Andreas
          • bug#82077:... Hugo Buddelmeijer via Bug reports for GNU Guix
            • bug#8... Hugo Buddelmeijer via Bug reports for GNU Guix
              • b... Andreas Enge
              • b... Andreas Enge
              • b... Hugo Buddelmeijer via Bug reports for GNU Guix
              • b... Sharlatan Hellseher
              • b... Hugo Buddelmeijer via Bug reports for GNU Guix
              • b... Andreas Enge
              • b... Hugo Buddelmeijer via Bug reports for GNU Guix
              • b... Sharlatan Hellseher
              • b... Hugo Buddelmeijer via Bug reports for GNU Guix
  • bug#82077: Close Andreas Enge

Reply via email to