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) [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

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.

Checking after a year. Has there been some change in upstream?

4 commits in 2020, no chance to have this ported to python3. From a maintenance point of view, I've been bundling more and more python2 packages to keep offlineimap functional.
That being said, the software is pretty mature and functional, I'm using it on a daily basis without any issue (if that matter).

That might be too pessimistic.
https://github.com/OfflineIMAP/offlineimap3 has a bunch of recent activity.

I wasn't aware of that project, thanks!

FWIW:
- it looks like offlineimap3 will be in Debian testing: https://github.com/OfflineIMAP/offlineimap3/issues/10
- this is the last package in Fedora that needs python2-six

I'll have a look at offlineimap3 packaging.

https://src.fedoraproject.org/rpms/offlineimap/pull-request/5

offlineimap-7.3.3-5.20200310git1e7ef9e7e6952f5d29ef0f5c25fd062798de55f3.fc35 is now a no-arch, Py3 only package.
It's based on the  https://github.com/OfflineIMAP/offlineimap3 project pointed out by Petr Viktorin and a few patches that are still in review upstream (actually the same as the one from the ArchLinux package https://aur.archlinux.org/packages/offlineimap3-git/)