Hi, On Sun, 30 May 2021 at 15:27, Mark H Weaver <m...@netris.org> wrote: > zimoun <zimon.touto...@gmail.com> writes:
>> The package offlineimap will go sooner or later since Python 2 is EOL. >> The migration from Py2 to Py3 is not clear [1] and the README [2] says: >> >> > As one of the maintainer of OfflineIMAP, I'd like to put my efforts into >> > [imapfw](http://github.com/OfflineIMAP/imapfw). **imapfw** is software in >> > development that I intend to replace OfflineIMAP with in the long term. >> > >> > That's why I'm not going to continue OfflineIMAP development. I'll >> continue >> > to maintain OfflineIMAP (fixing small bugs, reviewing patches and >> merging, >> > and rolling out new releases), but that's all. > [...] >> 1: <https://github.com/OfflineIMAP/offlineimap/issues/670> >> 2: >> <https://raw.githubusercontent.com/OfflineIMAP/offlineimap/master/README.md> > > Thanks for bringing this to our attention. > > Incidentally, I used 'offlineimap' for several years, and one day it > stopped working for me with an inscrutible error ("invalid literal for > int() with base 10: ''") , and I was never able to get it working again. > > I eventually switched to 'mbsync' from the 'isync' package, and it has > been working very well for my purposes. Since ’isync’ seems the standard replacement of ’offlineimap’, I propose to remove ’offlineimap’. For example, add a news entry and deprecate it, wait X months, and complete the remove. WDYT? Cheers, simon