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 mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
