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 offlineimap'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 offlineimap.
If you need anything from us, or something is unclear, please mention it here.
1. it's an app, written in python 2
2. hazy. upstream lists it as 'experimental', known broken, and does not appear to be actively working on it
3. churn through it, mostly. Since it's a giant wrapper around an internet protocol, i suspect str/bytes will be the fun part, but I haven't looked yet.
And do you have a plan to work on this package? It is a leaf package (nothing depends on it in rawhide) so we can retire it if there is no plan to make it work with Python 3.
Either I need to port it, or I need to keep a hacked up build for myself.
Thanks for the info. You are right, there are some old issues with Python 3 compatibility and nobody is working on them. Moreover, it seems that this tool will be replaced by imapfw so I don't think that investing our time to Python 3 compatibility is a wise idea.
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) . 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).
imapfw is actually *more* dead upstream. At least, he's not pushed anything in two years.
Can we get a FESCO exception for this or would it just be delaying the inevitable? I'm using actively using offlineimap and I'd hate it to go away, but I really *don't* have the capacities to port it to python 3.
It can definitely get an exception. You can take a look at existing requests for inspiration: https://pagure.io/fesco/issues?status=Closed&tags=python+2+exception
On the other hand, somebody will have to do the work because the exception won't last forever. It seems that offlineimap has experimental support for Python 3 with a few known issues so the porting won't start from scratch. You can also try to package it for rawhide and see whether the known issues affect your usage.
Trying to package it for py3 without porting would be a waste of time, the entire IMAP protocol usage has str/bytes confusion.
Ticket filed here: https://pagure.io/fesco/issue/2274
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.