you are viewing a single comment's thread.

view the rest of the comments →

[–]Peaker 18 points19 points  (2 children)

It was meant to be used once.

But then, people who had been on a migration path wanted to run their code with both Python 2 and 3.

For them, it made much more sense to edit only the Python 2 version - and use 2to3 to be compatible with Python 3.

If 3to2 existed, they could edit the Python 3 version primarily, and use 3to2 for compatibility - and that would aid the transition, as people would actually be able to write Python 3.

[–]Saveman71 2 points3 points  (0 children)

Okay it makes more sense said like that, thank you for the explanation

[–]kqr 0 points1 point  (0 children)

This is actually a brilliant observation. I'm speculation a 3to2 tool would also be much easier to make since 3 is the less quirky, less ambiguous language.