Hi Python Team, hi Guix,
I’ve started working on packaging the "next" Python.
I realize that it might not make sense, for Guix and the Python Team, to work on
this, and that it might have been better to help on getting the branch merged,
but my
professional use case for Guix is "having at least the same Python version as in
Debian", so I had to take some time to work on that. Sorry!
In Debian:
- The current stable is Bookworm and it contains Python 3.11.
- Next stable is Trixie and it will contain Python 3.13. It should be released
later this year.
In Guix:
- We currently have 3.10 as the default python.
- The `python-team` branch has 3.11.
- We have 3.12 has `python-next`.
I have a working package definition for 3.13, but I’m struggling with the
inheritance
mechanism. I had to copy over from 3.12 the 300+ lines of `(arguments …)` to
make it work, even if I didn’t change a single line of it!? That sounds
sub-optimal to me. Oh, and those exact same lines seem to be coming from 3.11!?
The actual only difference is the `python-3.13-fix-tests.patch` file. I also
had to copy over the `(module …)` and `(snippet …)` for I didn’t know how to
properly inherit them. I would have loved to be able to just write the
following,
but somehow reality doesn’t follow!?
```scheme
(define-public python-3.13
(package
(inherit python-3.12)
(version "3.13.2")
(source
(origin
(sha256 (base32 "0mpbb6hkzdphyin861ywqnxibh5i4gjl5vvxdyralz6ngk2vr16r"))
(patches (search-patches "python-3-deterministic-build-info.patch"
"python-3.13-fix-tests.patch"
"python-3-hurd-configure.patch"))))))
```
Should I anyway submit a patch?
I also have a patch for 3.14, even if it’s still an alpha.
Would it make sense to have it anyway in Guix?
Thanks in advance for all the time and energy you can dedicate to this.
Best regards,
--
Tanguy
