So far #macOS Mojave ships with Python 2.7.10. I don't even want to rant about how this should be 3.6 by now.
What I'm disappointed by is that this is 2.7.10, a release from May 2015. Latest is 2.7.15. THREE YEARS of bugfixes since then! I hope Apple will fix it before 10.14.0.
Conversation
Show replies
I bet there’s literally nobody working on it. They should just kill it, it does more harm than good.
1
2
I recommend ‘brew install python’ and ‘brew install pipenv’ always up to date and let’s me isolate my projects.
1
You should give a try to Fedora (28) which has python3 by default, not "python" (python2) by default. python3 is 3.6.5 and python 3.7 is already available (yep!).
2
12
To be fair, it's going to be pretty hard to type those new f-strings with a broken f-key.
2
2
35
This Tweet was deleted by the Tweet author. Learn more
That rationale would make sense if you're keeping the latest bugfix release of Python 2.7 (which is 2.7.15 at the moment) for legacy reasons. It doesn't hold if your shipping an outdated bugfix release. That just means it's more broken than necessary.
3
What TLS versions does the SSL module support. If they haven't updated the SSL libraries and doesn't support recent TLS versions that sites would require be used, what is the point.
1
2







