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 taskcoach'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 taskcoach. If you need anything from us, or something is unclear, please mention it here. Thank you.
Taskcoach is an application written in Python 2. Upstream doesn't appear to be moving particularly fast to upgrade to Python 3. Upstream ticket: https://sourceforge.net/p/taskcoach/bugs/1674/ I don't have any particular interest in porting it to Python 3, so this is probably a candidate for retirement from Fedora.
Then, could you please retire it in rawhide?
I think perhaps I'll wait until F32 to retire it, to give upstream more time.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
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
> I think perhaps I'll wait until F32 to retire it, to give upstream more time. This is the last unorphaned package that drags in Twisted. Can we do a compromise and retire it once nothing else needs twisted? That should be in around 5 weeks.
(In reply to Miro Hrončok from comment #6) > > I think perhaps I'll wait until F32 to retire it, to give upstream more time. > > This is the last unorphaned package that drags in Twisted. Can we do a > compromise and retire it once nothing else needs twisted? That should be in > around 5 weeks. Sure!
Python 2 Twisted just got removed.
I've retired the package on master.