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 childsplay'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 childsplay. If you need anything from us, or something is unclear, please mention it here. Thank you.
As mentioned in the pyfribidi bug, bug 1738044, childsplay is an app written in python2 and its upstream has no plans to port it to python3, therefor we have retired childsplay for F31+. I'm closing this bug, since childsplay has been retired for F31+.
Shouldn't childplay just be retired for F32+ , i.e. after branched F31 ?
(In reply to Sergio Monteiro Basto from comment #2) > Shouldn't childplay just be retired for F32+ , i.e. after branched F31 ? You can do it at any moment. It depends on you whether you want to have it in F31 or not. It might make sense to drop some packages now and the rest later to catch all possible problems sooner than later.
(In reply to Sergio Monteiro Basto from comment #2) > Shouldn't childplay just be retired for F32+ , i.e. after branched F31 ? As mentioned in the original description Python 2 reaches EOL (no more security updates) during the lifetime of F31, so it is desirable to get as much Python 2 packages removed from F31 as possible. Dropping this now also allows me to focus on other Python 2 packages which I do want to keep alive.