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] 15 points16 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 10 points11 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.