The first OS I've used that includes Python3 in the base install is Debian 8(Jessie) and I no longer use Debian in production. CentOS 7 does not include Python3 in the base install. You can install it, sure, but why bother when you can just use the python that is already there? Or better yet, /bin/bash...
Again, in the context of this discussion, the whole argument is yet another point in shell's favor. There's no major backwards-incompatible change in the language. With Bash, you just decide whether POSIX compliance is something you need, and that's basically it. Both versions are still supported and no one interrupts discussions to announce that beatings will continue until morale improves whenever the deprecated version of Python comes up.
Re:Things I Wish I'd Known About Bash
by mixmastamyk on Sunday January 21, 2018 @04:36PM
(#16200172)
If you are using a ten year old software and can’t install a package, that’s your problem. Quit acting like it is the default situation.
Or you could put the wrapper functions in a module and call it a day, either way problem solved.
Re:Things I Wish I'd Known About Bash
by mountainerd on Tuesday January 30, 2018 @12:44PM
(#16267220)
He's not acting like it's the default situation. For the distributions he mentioned, it is the default situation.
Is there a reason you cannot just say `#!/usr/bin/env python3` in your scripts? I don't see why you require python3 to be the default, am I missing something here?