Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for python-gtkextra's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to python-gtkextra. If you need anything from us, or something is unclear, please mention it here. Thank you.
(In reply to Lumír Balhar from comment #0) > - What is the reason for the Python2 dependency? (Is it software written in > Python, or does it just provide Python bindings, or use Python in the build > system or test runner?) - The package is a binding for Python 2 implemented in C - Depends on PyGTK, for GTK2 > - What are the upstream/community plans/timelines regarding Python 3? Upstream is dead enough (5 years with no activity) > - What is the guidance for porting to Python 3? (Assuming that there is > someone who generally knows how to port to Python 3, but doesn't know > anything about the particular package, what are the next steps to take?) - Don’t do it; does anyone care? The only user per repoquery is audit-viewer, which can be removed along with this. - If you really wanted to: - Port gtkextra to GTK 3 (or maybe use the https://github.com/fpaquet/gtksheet subset; no idea how the GTK 3 support is in there) - Replace use of PyGTK with PyGObject - Then see what other work is left to do.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Given that you are a maintainer of this package and the only package that depends on them, could you please retire both in Fedora rawhide?
The current plan is to remove packages with dependency on Python 2 from Fedora 32 in the middle of November 2019. If you want to keep your package in Fedora after that date and you cannot port it to Python 3 yet, you need to request a FESCo exception for the package and all its Python 2 dependencies (even transitive) [1]. If you don't want to maintain it anymore, and nothing in Fedora uses it, you can retire it or just remove the Python 2 part from it (subpackage, module, bindings, etc.). If you're considering filing the exception request, let us know. We can help (for example, we can help find all the dependencies). [1] https://fedoraproject.org/wiki/Changes/RetirePython2#FESCo_exceptions
*** This bug has been marked as a duplicate of bug 1775073 ***