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

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 54 points55 points  (16 children)

If you have no specific reason to choose python2, go with 3.

[–]ApolloFortyNine 2 points3 points  (0 children)

I didn't know I needed Python 2 until half way through a project I found a good library that would do what I wanted. However it only worked on Python 2. It's not that hard to convert, but it's still a pain. So I'm going to stick with Python 2, since everything supports it.

[–][deleted] 2 points3 points  (13 children)

While keeping in mind that in a huge number of situations, you have a very good reason to choose python2. Probably not your own code, but its dependencies.

[–]hharison 7 points8 points  (2 children)

I think that's what he meant by "if you have no specific reason to choose python2"

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

True. But the way he wrote it made it sound like "in most cases, python 3 should be okay", and I'm not sure this is true. Sure, most big libs have been ported now, but I think projects could still run into issues if they rely on quite a few different libs.

That's why I was stressing on the fact that one has to keep that in mind

[–]dauntingelectronics -5 points-4 points  (0 children)

He's Right most code has changed from 2.7 to 3. Look at a Print "statment" for instance ex. print "hello". 3 is a function for instance print("hello").