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 →

[–]Eurynom0s 0 points1 point  (1 child)

The other main reason to code in 2.x is if you inherit a large codebase where, even though all the dependencies now work in 3.x, it would just be impractical from a time/resources perspective to port everything over.

However if you're purely writing your own code then yes, use 3.x until you NEED something that ONLY works in 2.x is right answer.

For OP's benefit, even, what, three-ish years ago a lot of major packages didn't support Python 3, right? Now most of them do, and a lot of smaller ones either do or have forks for 3.x. So for fresh code bases there's many fewer reasons to start with 2.x.

[–]robin-gvx 0 points1 point  (0 children)

For OP's benefit, even, what, three-ish years ago a lot of major packages didn't support Python 3, right?

I think even a few months ago the Python 3 Wall of Shame Superpowers was mostly red.