Python 2.7 is EOL on January 1st, 2020, after which security upgrades will cease. And there are still regular security patches to Python 2.7. This is also an issue for the dependencies like twisted.
Is there a TODO somewhere on guidance for migration to Python 3.7?
It looks like the most efficient option would be to clone, get things running under six, then make a final migration to Python 3.7.
At the very least, I'd suggest recommending that users run their CalendarServer instance behind a reverse proxy that has mod_security and modern crypto methods and ciphers configured.
I've thought about sidestepping this issue and adopting other options for a calDAV+cardDAV server like sabre/dav, inverse-inc/sogo, or Kozea/Radicale. But this project is the only one I'm aware of that has iMIP, DKIM integration, and a decent code base (not PHP, thank you…) to make python3 migration worth the effort.
Python 2.7 is EOL on January 1st, 2020, after which security upgrades will cease. And there are still regular security patches to Python 2.7. This is also an issue for the dependencies like twisted.
Is there a TODO somewhere on guidance for migration to Python 3.7?
It looks like the most efficient option would be to clone, get things running under six, then make a final migration to Python 3.7.
At the very least, I'd suggest recommending that users run their CalendarServer instance behind a reverse proxy that has mod_security and modern crypto methods and ciphers configured.
I've thought about sidestepping this issue and adopting other options for a calDAV+cardDAV server like sabre/dav, inverse-inc/sogo, or Kozea/Radicale. But this project is the only one I'm aware of that has iMIP, DKIM integration, and a decent code base (not PHP, thank you…) to make
python3migration worth the effort.