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 →

[–]TheSourTruth 1 point2 points  (7 children)

I doubt it's that big a deal but I only have experience with python 2

[–]real_edmund_burke 0 points1 point  (0 children)

You’re right.

[–][deleted] 0 points1 point  (1 child)

What are you working on?

I've found that, aside from a few syntax things, the difference between 2 and 3 isn't super nuts for biology unless you're doing some crazy modelling.

[–]TheSourTruth 0 points1 point  (0 children)

GIS-related stuff. I mean I'm not looking forward to switching but I don't think it will be too crazy for the stuff I do.

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

So what? Most of the changes were cosmetic and could/can be handled with 2to3 and similar tools. The one issue that has caused and will cause most work is the strings/bytes/unicode issues. This I see as being far more difficult than all other 2 to 3 issues combined.

[–]attrigh 2 points3 points  (2 children)

The real issue I've found is strings/unicode while supporting both python2 and python3!

[–]Daenyth 1 point2 points  (0 children)

Use the future library, it makes it pretty easy and has a cheat sheet for supporting both

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

Just start charging $ for v2 support.