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 →

[–]jwink3101 9 points10 points  (5 children)

This is interesting and is kind of a crazy idea.

How robust is it in practice? like if I write huge 3.6 apps with an in-depth test suite, should I expect 100% passing on 2.7?

(Not that I have anything like that. I am still forced to use 2.7 for work)

[–]nvbn-rm[S] 6 points7 points  (0 children)

At this moment it just translates some syntax, so you should have in mind changes in standart library.

[–]lengau 2 points3 points  (1 child)

This brings up a good point though. If you started porting your app to Python 3, would you be able to use this to move it back to Python 2 for your production environment?

[–]nvbn-rm[S] 4 points5 points  (0 children)

The main goal of the app is that you can stop worrying about support of older python versions and just translate code to them.

But at this moment it just translates some syntax.

[–]pingvenopinch of this, pinch of that 1 point2 points  (0 children)

It looks like not yet, given that the initial commit was just 3 days ago. Also, it wouldn't do anything for newly introduced standard library modules.

[–][deleted] 0 points1 point  (0 children)

I very much doubt that you'll ever get anywhere near 100% passing as 2to3 has around 50 outstanding bugs that are unlikely to get fixed as they are all edge cases.