Drop python2 support after 3.1 #6537
Description
As we all probably know, python 2 is EOL, so it might be time to drop support for it.
We currently use python in a few places:
- webconfig
- manpage completion generation
- the docs (sphinx + configuration + our fish_indent_lexer)
- littlecheck
- some completion scripts (npm, bower, yarn, composer - anything that needs json)
All of which are optional and should fail cleanly if python isn't installed.
What I am proposing is that we stop explicitly checking and supporting python 2, and we start recommending python 3 (we already use it over 2 if available), after 3.1 is released. Nothing too rash, if an issue pops up we can still fix it, and if it's just cosmetics we should still prefer allowing python 2 to work.
Or we could take a more extreme stance and improve our code actively with things that don't work in py2, or only do that for some things.