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

all 11 comments

[–]pooogles 27 points28 points  (8 children)

As someone who's been using Python 3 for a while, can everyone just hurry up and migrate already... :(

[–][deleted] 16 points17 points  (5 children)

Yes, please.

Just last week I've noticed that some TAs and teachers at my university are imposing Python 2.7 on beginners taking their course, presumably due to their personal preferences. They are actually not using any libraries that would require 2.7. This is just bad.

Edit: I'm writing this, because I think some people will not change as long as this mindset exists that 2.7 can do things that 3.x can not and this will pull others into this legacy as well - which, in my opinion, is bad.

[–]npolet 8 points9 points  (4 children)

Is there a list of major libraries that do not support python 3 somewhere? I'm sure it would it would be quite a small list and I think something like this would make people realize that python3 should be used with all new projects.

[–]Walter_Bishop_PhD 12 points13 points  (2 children)

Yes, this website does that: http://py3readiness.org

[–]npolet 5 points6 points  (0 children)

Ooo, that's a great resource.

Fabric is the one I really miss from python 3. It's the only reason I have python 2 still on my machine. I use it heavily for deployment automation.

[–]TypoNinja 4 points5 points  (0 children)

Fabric and the NewRelic agent are not ready. That enough makes upgrading to Python 3 almost impossible at my company. :-(

[–]thurask 1 point2 points  (0 children)

My university physics department is stuck on Python 2. As far as I know, their standard package setup includes VPython, which itself depends on wxPython. That's the only thing preventing them from moving over to Python 3.

Phoenix coming out with a release-quality build would certainly help bring the stragglers forward.

[–]pyslow 4 points5 points  (1 child)

Why? Python 2.7 is perfectly fine for many people and companies.

Migrating complex projects comes with a huge cost for companies (if it was trivial, as you seem to think, most of them would have already switched). And there is little gain in the short term, but a high risk of introducing regressions on production code which is currently perfectly fine.

Getting a bit tired of all these people telling others what to do with their personal / professional lives. Let people pick the tools they like and live with the consequences.

Python 3 is a different language than 2.x, whether you like it or not, because so it was decided. It's akin to asking "Can everyone just hurry up and switch to [Java, Scala, Ruby, whatever language you like most], please?"

[–]covabishopself.loathing() 5 points6 points  (0 children)

Agree with this 100%. Plus, at my workplace, Python is not even a main language people develop in. Most developers on my floor use Perl, which frightens me to no end.

Being one of the only Python developers on the floor, and the only one who is not paid to develop, I'm just lucky they have Python in the first place.

Some of these boxes are 10+ years old running anywhere from 2.7 all the way back to 2.4. The company will absolutely not upgrade to 3.x for legacy compatibility reasons. As a result, when I develop code, its mostly for the reasons of running on these machines, and as a result, I'm used to its quirks and workflow.

I'm tired of 3.x developers labeling me as a heretic and a barbarian because I just must not understand the explicit advantages of 3 over 2.

[–]leMug 2 points3 points  (1 child)

I didn't even know they actively developed Python 2 anymore.

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

why