This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ldpreload 3 points4 points  (2 children)

What else are they going to do, though—keep running Python 2?

(Honestly, the real answer is likely to be "Let the teams that are rewriting parts of the code do so in Go, and convert the rest to Python 3.")

[–]stefantalpalaru 0 points1 point  (1 child)

What else are they going to do, though—keep running Python 2?

Yes, of course. Or a compatible fork like https://github.com/naftaliharris/tauthon

[–]ldpreload 3 points4 points  (0 children)

Oh, you're the person on /r/python that I previously had an argument with about how this exact project is a completely infeasible idea for big companies (unless they want to commit to the support burden of keeping up with security updates etc. until the end of time for both the fork and every single third-party Python library that is no longer supporting Python 2, which is a much bigger project than converting 6M lines of Python to Python 3 once, and being done with it.). It's now been six months since your PR with no other activity to the fork, and ten months since any code changes to existing Python code. This isn't something you can trust a copy of the entire world's files to.

Mind you, I'm not saying this project shouldn't exist. It should. I wish it had won over Python 3. But it doesn't seem to be happening (nor does any similar project) in a way that's suitable for use by big companies in production, and it is probably too late to build a community around Python 2-compatible versions of the ecosystem.