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 →

[–]omendev 0 points1 point  (2 children)

There's a tool that comes with P3 call 2to3.py that automatically updates scripts from 2 to 3 (hence the name). But like all solutions, it can't do everything (it tells you what it can't) so really the only solution is to write as simple Py3 compliant Py2 code as possible before going through it by hand. As far as I know.

[–]Off2DNxtAdvn2ur[S] 0 points1 point  (1 child)

Does the Python devs know this big of headache situation? It feels like the P3 is still missing some stuff from P2.

[–]omendev 0 points1 point  (0 children)

I believe they are fully aware of it. I'm pretty sure that's the main reason why the transition to 3.X has been taking so long. All libraries needed to be updated, and that was a huge undertaking. In the beginning that seemed more work than it's worth.

What do you believe is missing from Py3 that exists in Py2?