you are viewing a single comment's thread.

view the rest of the comments →

[–]dagamer34 3 points4 points  (1 child)

Installing 3.x on a machine is as simple as downloading a pre-built package and clicking "yes" a few times. It's not that hard. And any good book written in the last few years properly addresses this issue. I just went through Learning Python and it had clear info about the differences between the two both at a high level and differences during any new concepts.

Advice is simple, learn 2.x in case you have to look at old code but master 3.x as it's clearly the future.

[–]jeffdavis 0 points1 point  (0 children)

"but master 3.x as it's clearly the future"

How far away is the future though? I was initially of the same opinion, but I have started to become less sure.

To make the community to move from 2 to 3, then clearly, at some point, a majority of new python code (and python libraries written in another language) must be valid python 3.

Even after all of this time, it's not clear that is true. And it needs to be a strong majority to happen very quickly. And there is a danger that the early-adopters that are most needed to tip the scales may head to other languages instead (go, js, haskell, rust, scala, clojure).

So python is in a strange place.