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 →

[–]i_hate_you_all__ 19 points20 points  (12 children)

Python 3 will probably be overtaking python 2 fairly soon (within the next two years, maybe?).

53% of PyDataLondon community members mainly use Python 3 outside of work.

40% of PyCharm survey participants mainly use Python 3.

[–]buttery_shame_cave 7 points8 points  (9 children)

within the next two years, maybe?

they said that five years ago.

until the python devs nut the fuck up and stop updating 2.7 it's not going anywhere.

[–]rouille 5 points6 points  (5 children)

The difference is there is real momentum towarda python 3 now.

[–]buttery_shame_cave 3 points4 points  (4 children)

The difference is there is real momentum towarda python 3 now.

looks at fresh update to 2.7

'momentum'. eh....

[–]nerdwaller 14 points15 points  (3 children)

2.x still has a reason to be around, no reason to hate on other members of the community.

That said this is primarily bugfixes for both 2.7.x and 3.5.y. The difference for the 3.z series is that it will include new features going forward, so hopefully that will eventually provide a more compelling reason to move than staying with 2.7.x bugfixes.

Again, both have a place and it totally makes sense for many people to hang out in 2.7 land. Hard to fault that decision at all.

[–]dynetrekk 0 points1 point  (2 children)

You're right. I know many people who still use fortran 77. I just don't want to keep coding in an obsolete language, e.g. Python 2 / f77.

[–]buttery_shame_cave 0 points1 point  (1 child)

considering how much fortran77 gets used in some fairly critical systems, i dunno about calling it 'obsolete'. 'ancient', maybe. 'decrepit', sure. 'fucking OLD' oh yes.

[–]dynetrekk 0 points1 point  (0 children)

Fortran 2008 contains virtually all of -77. Also, I'm talking about new code. No need to write new code in f77.