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 arandr's future. Specifically:
- 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 arandr.
If you need anything from us, or something is unclear, please mention it here.
It seems that the latest version 0.1.10 is compatible with Python 3 so the package can be updated and drop Python 2 support.
Please answer the above questions. If you don't the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages
If you need any information or help, please let us know.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
See also https://pagure.io/releng/issue/8686
I can confirm that the latest build of arandr (arandr-0.1.10-1.fc32) does not depend on Python 2.