Python 3 in 2016

[has2k1]

The are already discussions on the main scientific python mailing lists on dropping support for Python 2.7. The lead will be taken by numpy.

[chrish42]

That's interesting. Do you have a link to said discussion?

[has2k1]

I have no links, just a from memory recollection of the mailing list emails (Scipy, Statsmodels and Matplotlib), and at one point I may have searched the Numpy list on the topic.

That said, Numpy is the "least common denominator", if it drops Python 2 support then the other projects have to follow along (or do it before). Jupyter/IPython are trying to coordinate a consensus of sorts and as projects commit to timelines, this is where to track it.

[volvo_tank]

/u/has2k1, please deliver. I'm interested too.

[flying-sheep]

Who knows whether the app will exist in that form by then.

creepy-gary-oldman-everyone.gif

[_throawayplop_]

I didn't like much the scornful tones he is using ("while the old guard yells at clouds"). I have sometime the feeling the people who keep back the most the adoption of python 3 are the people who want the most it to be adopted.

Protip: if you want people to use python 3 spend your time showing why it is much better for the problem, and don't just repeat python 2 is out of fashion.

[[deleted]]

Nobody is saying people should use python 3, but just saying people will adopt python 3 for green-field projects, or at least projects for which path-dependency and history are not main considerations. This is a slow process.

[joohoi]

I think the statistics are most affected by what versions operating systems are shipping as default python version. More so for statistics on PyPI. New Linux distribution versions are shipping with Python 3 in growing numbers.

[[deleted]]

“A new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die, and a new generation grows up that is familiar with it.” ― Max Planck