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 pyifp'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 pyifp. If you need anything from us, or something is unclear, please mention it here. Thank you.
> 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?) As the description says, it's "Python Bindings for libifp." It's used to access some old iRiver iFP MP3 players over USB. The upstream project has been dead since 2006, when Python3 did not exist. > What are the upstream/community plans/timelines regarding Python 3? The upstream timeline regarding Python 3 is never. > 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?) Porting to Python 3: this is a tiny project with two SWIG interfaces and a single handwritten API sitting on top of the autogenerated wrappers. It could probably be ported to 3 relatively easily by someone who knows 3; I don't.
> It could probably be ported to 3 relatively easily by someone who knows 3. If someone ports it, is there way for them to test that it still works?
I have one of these devices and would be happy to test a Python 3 port for them, if that helps.
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.
Do you think it's worth it to invest time to porting this package to Python 3? 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'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
(In reply to Lumír Balhar from comment #6) > Do you think it's worth it to invest time to porting this package to Python > 3? Probably not. I'm still saddened by the de jure wholesale removal of Python 2 in Fedora.
*** This bug has been marked as a duplicate of bug 1775068 ***