What is the Fedora policy regarding Python 2 packages in F33?
If there was a Fesco exception for some package last year can we assume that we can/should keep the package also in F33? I did not find anything about the assumed scope of these Fesco exceptions.
Specifically this is about bug 1737930: https://bugzilla.redhat.com/show_bug.cgi?id=1737930#c44
We added a conditional in babel so the Python 2 subpackage is not present anymore in master/F33. However trac maintainers ask if we could re-add the Python 2 package for babel in rawhide.
Should I do that?
Non-issues: - Babel supports Python 2 just fine. I could re-enable/maintain the subpackage without major issues. - For some (non-Fedora) $PROJECTS I'm still using Python 2 so I have sympathy for other who need Python 2 as well. I'm not on a crusade to wipe Python 2 from Fedora.
Felix
On 07. 05. 20 23:35, Felix Schwarz wrote:
What is the Fedora policy regarding Python 2 packages in F33?
If there was a Fesco exception for some package last year can we assume that we can/should keep the package also in F33? I did not find anything about the assumed scope of these Fesco exceptions.
Most of the exceptions don't have a deadline set. The one with babel certainly doesn't. We will be happy to have trac ported to Python 3 (it is the last Python 2 app in Fedora designed to be possibly internet facing -- and security of Python 2 will become major PITA), but until that happens, as long as you are happy to keep shipping pytohn2-babel, you can.
Specifically this is about bug 1737930: https://bugzilla.redhat.com/show_bug.cgi?id=1737930#c44
We added a conditional in babel so the Python 2 subpackage is not present anymore in master/F33. However trac maintainers ask if we could re-add the Python 2 package for babel in rawhide.
Should I do that?
Depends on you. The exception has this covered. Splitting to a separate component is also possible (in case babel can no longer be updated in single component, etc.).
Non-issues:
- Babel supports Python 2 just fine. I could re-enable/maintain the subpackage without major issues.
For now. Once this is no longer true, a sepearate component might be the only option (in any case, please don't package two different babel versions from the same spec, but I guess you wouldn't).
Also note that as Python 3 moves forward, single code-base will eventually get trickier and trickier. We've managed to postpone the removals of some long deprecated py2 compatibility from Python 3.9 to 3.10, but the message was pretty strong: No more further delays.
However, that second thing is more a concern for babel upstream. Either they will manage somehow, or they'll split. When they split, we need to split as well.
- For some (non-Fedora) $PROJECTS I'm still using Python 2 so I have sympathy for other who need Python 2 as well. I'm not on a crusade to wipe Python 2 from Fedora.
What crusade are you talking about? I'm just kidding.
python-devel@lists.fedoraproject.org