The macOS part is done now on travis and everything worked as expected so far.
The only remaining thing is that versioning the DB could improve the startup time by a bit by skipping the py2 upgrade, but I don't care enough right now.
1) For 3.10: Switch the official Windows build to Python 3
2) Collect/Fix errors
3) For 3.11: Switch the rest
4) After 3.11: Drop Python 2 support
lazka
All 6 comments
It came up on IRC that maybe we just switch everything at once (and maybe call it 4.0 so breakage is a bit expected?)
lazka
on 8 Aug 2017
...though we might want to have some "big features" for 4.0 too, of course, to balance out all those "new" bugs...
declension
on 8 Aug 2017
Timing seems good, with Ubuntu 17.10 (now out) officially dropping PY2.
declension
on 24 Oct 2017
Timing seems good, with Ubuntu 17.10 (now out) officially dropping PY2.
Many of our dependencies aren't on the default ISO, so this doesn't change much.
lazka
on 25 Oct 2017
If there are any remaining 4.0 issues, please add them to the 4.0 milestone
lazka
on 29 Oct 2017
Debian/Ubuntu PPA switched to py3
edit: opensuse/fedora as well now
edit2: arch aur as well
lazka
on 31 Oct 2017
Related issues
lixoo81
路
4Comments
marcelpaulo
路
4Comments
jeronimojoe
路
5Comments
lazka
路
6Comments
lazka
路
4Comments
Most helpful comment
Debian/Ubuntu PPA switched to py3
edit: opensuse/fedora as well now
edit2: arch aur as well