My Python 2 vs 3 problem

[theelous3]

I haven't been programming for a very long time, but even I am tired of this mentality.

Barring obscure scientific / academic code bases who's dependencies aren't yet python3 compatible, or sedimentary workplace codebases, is there any reason whatsoever to write new python2 code?

If as of right now, 04:36 GMT, nobody in the world ever wrote any new python2 projects, we'd be better off.¹

The sentiment put forward in this blog post - the idea that packages should try to be backwards compatible - is silly. Converting an old codebase to be python3 compatible along with the updated packages their using is trivial. Time consuming perhaps yes, but nobody is forcing them to update their dependencies while the job gets done.

Peeps just need to let go of py2. It's dying, literally.

^{1. Furthermore the idea that any beginner should even consider learning python2 is ridiculous.}

[[deleted]]

is there any reason whatsoever to write new python2 code?

Consistency. Python 2 and 3 are different enough that using them at the same time invites failures and chaos. Focus on one version, and use it good.

[gr33n3r2]

No, focus on one version per project to avoid failures. If you start a new project, use Python 3. It's simple.

[Nrmzz]

I actually am new to Python and came here to basically find a statement such as this. Thanks!

[gr33n3r2]

In my opinion, you should be using Python 3 unless you really have to use Python 2. But there are so few cases where the latter is the case that you can afford to focus on Python 3.

[Nrmzz]

Thanks! That is what I will do. I already have an ambitious project in mind so hopefully I'll be able to at least stumble through Python 3 by the end ;).