Hello,
To make the Python offering complete in EL, we've decided to bring Python 3.13 to EPEL 10.1 and 9. Now you can test it out. (We don't currently plan to add it to EPEL 10.0, so if you have a strong case for that, please speak up).
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6ebd046d4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b777af3d6c
We plan to rebase the Pythons to every new upstream version and keep it synced in all active branches (similarly to how we do it in Fedora). We don't plan to add more packages to the stack, but if you need some, you can do so yourself.
Cheers, Karolina Surma (she/her/hers) Senior Software Engineer Python Maintenance Team, Red Hat
On 6/27/25 04:10, Karolina Surma wrote:
Hello,
To make the Python offering complete in EL, we've decided to bring Python 3.13 to EPEL 10.1 and 9. Now you can test it out. (We don't currently plan to add it to EPEL 10.0, so if you have a strong case for that, please speak up).
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6ebd046d4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b777af3d6c
We plan to rebase the Pythons to every new upstream version and keep it synced in all active branches (similarly to how we do it in Fedora). We don't plan to add more packages to the stack, but if you need some, you can do so yourself.
Cheers, Karolina Surma (she/her/hers) Senior Software Engineer Python Maintenance Team, Red Hat
Thank you, it is much appreciated.
On 27. 06. 25 12:10, Karolina Surma wrote:
Hello,
To make the Python offering complete in EL, we've decided to bring Python 3.13 to EPEL 10.1 and 9. Now you can test it out. (We don't currently plan to add it to EPEL 10.0, so if you have a strong case for that, please speak up).
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6ebd046d4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b777af3d6c
We plan to rebase the Pythons to every new upstream version and keep it synced in all active branches (similarly to how we do it in Fedora). We don't plan to add more packages to the stack, but if you need some, you can do so yourself.
When the updates reach stable we plan to ship slight fixes for virtualenv:
epel10.1: https://src.fedoraproject.org/rpms/python-virtualenv/pull-request/136 epel9: https://src.fedoraproject.org/rpms/python-virtualenv/pull-request/137
And python3.13-rpm:
epel9: https://src.fedoraproject.org/rpms/python3-rpm/pull-request/20 epel9-next: https://src.fedoraproject.org/rpms/python3-rpm/pull-request/19 epel10.1 todo
Karolina Surma venit, vidit, dixit 2025-06-27 12:10:22:
Hello,
To make the Python offering complete in EL, we've decided to bring Python 3.13 to EPEL 10.1 and 9. Now you can test it out. (We don't currently plan to add it to EPEL 10.0, so if you have a strong case for that, please speak up).
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6ebd046d4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b777af3d6c
We plan to rebase the Pythons to every new upstream version and keep it synced in all active branches (similarly to how we do it in Fedora). We don't plan to add more packages to the stack, but if you need some, you can do so yourself.
Hi there
I'm a bit confused by those two statements in combination:
I understand "rebase python to python 3.13" as `python` being `python3` being `python3.13`. In this case, the whole stack needs a rebuild, doesn't it?
In contrast, providing "a python 3.13 environment" would mean provding just the versioned `python3.13` and some versioned packages `python3.13-*` enough for a tox 3.13 env or such.
I know it's "just in EPEL", but as soon as someone builds an EPEL package against it, that package pulls in python3.13. And if it's really a rebase then ...
Cheers Michael
Hi there
I'm a bit confused by those two statements in combination:
I understand "rebase python to python 3.13" as `python` being `python3` being `python3.13`. In this case, the whole stack needs a rebuild, doesn't it?
Hello,
I'm sorry, I see where the confusion came from. The main python (python3) is/will not be changed. The precise statement is: we will rebase Python 3.13 to each new upstream version when they're released in all of the EPEL branches.
In contrast, providing "a python 3.13 environment" would mean provding just the versioned `python3.13` and some versioned packages `python3.13-*` enough for a tox 3.13 env or such.
This is what happens in EPEL 9 and 10 with Python 3.13.
Karolina
Karolina Surma venit, vidit, dixit 2025-07-04 11:36:43:
Hi there
I'm a bit confused by those two statements in combination:
I understand "rebase python to python 3.13" as `python` being `python3` being `python3.13`. In this case, the whole stack needs a rebuild, doesn't it?
Hello,
I'm sorry, I see where the confusion came from. The main python (python3) is/will not be changed. The precise statement is: we will rebase Python 3.13 to each new upstream version when they're released in all of the EPEL branches.
In contrast, providing "a python 3.13 environment" would mean provding just the versioned `python3.13` and some versioned packages `python3.13-*` enough for a tox 3.13 env or such.
This is what happens in EPEL 9 and 10 with Python 3.13.
Thanks for clarification. I'd say you rebase python3.13 to each new upstream *micro* version (with major=13 and minor=13 staying put).
It's important in the sense that python3.13 will remain present even in case you decide to bring Python 3.14 to those branches (as a new package python3.14).
HapPy packaging ;-)
Michael
epel-devel@lists.fedoraproject.org
-
Karolina Surma -
Michael J Gruber -
Miro Hrončok -
Orion Poplawski