Python 3.9 - Hackdot

Re:Python 3.9 by user5994461 on Tuesday October 20, 2020 @09:58AM (#24837340)

I was about to ask why would they do a release if they know it's broken and blowing up their flagship libraries? It's worrying when the interpreter starts to favor shipping quickly over being functional.

But nevermind, the 3.9 release was 15 days ago and the bug was identified 8 days ago. I guess there has to be a release before people will start using it and find bugs/regressions.

There's a saying to always wait for the .1 release, this is a good illustration of why.

[ Parent | on HN ]

Re:Python 3.9 by dec0dedab0de on Tuesday October 20, 2020 @11:19AM (#24838338)

I don't know if I would call the SciPy ecosystem the flagship libraries of python. I know it is very popular,and probably in the top 5 use cases, and I use some of them everyday. but in my experience they've always been off in their own world in relation to the rest of the python community. Most of the people I've met that use this stuff are either scientists or finance people that are just using it as another tool along with matlab, R, and excel. Which is what they should be doing, but in their minds they're not writing python code they're using Pandas, Jupyter, and Matplotlib.

But yes, never ever jump on a new release of anything, at least in production. Always stand back and wait for someone more optimistic to find the bugs

[ Parent | on HN ]

Re:Python 3.9 by dragonwriter on Tuesday October 20, 2020 @12:10PM (#24839057)

> I don't know if I would call the SciPy ecosystem the flagship libraries of python.

I mean, sure NumPy is integral to python finance and scientific computing...but it's also right at the heart of the popular Python roguelike tutorial, too.

There's Python code that doesn't use NumPy, sure (I've got some in production right now), but I can't personally think of a Python library with nearly as deep dependencies across nearly as diverse a range of use cases.

[ Parent | on HN ]

Re:Python 3.9 by raziel2p on Tuesday October 20, 2020 @10:21AM (#24837599)

What makes pybind a "flagship library"? If it was very widely used this bug probably would've been caught by people testing the alpha/beta/rc versions of 3.9.

[ Parent | on HN ]

Re:Python 3.9 by dragonwriter on Tuesday October 20, 2020 @10:36AM (#24837790)

> What makes pybind a "flagship library"?

NumPy, SciPy, and friends are, individually and collectively flagship libraries, and depend on pibind11.

> If it was very widely used this bug probably would've been caught by people testing the alpha/beta/rc versions of 3.9.

They are very widely used, but “probably” means “do enough releases and you will find exceptions”. Welcome to an exception.

[ Parent | on HN ]

Re:Python 3.9 by true_religion on Tuesday October 20, 2020 @10:27AM (#24837663)

People using numpy are not in the fringe. If this wasn’t triaged during prereleases then it’s either that it doesn’t always cause problems, or there is an issue in the diversity of testers.

[ Parent | on HN ]

Re:Python 3.9 by ictebres on Tuesday October 20, 2020 @10:36AM (#24837791)

the parent was probably talking about NumPy/SciPy/Tensorflow/PyTorch, which I would also label as flagship libraries...

[ Parent | on HN ]

Re:Python 3.9 by xiphias2 on Wednesday October 21, 2020 @07:50AM (#24846869)

I personally don't like Python (I prefer Julia/Ruby/Rust), but all the new advances in machine learning are implemented in Tensorflow and PyTorch, so I came back to Python just because of these libraries and infrastructure on top of them.

I was just using the expit function from scipy yesterday by the way, because that's where it was implemented.

[ Parent | on HN ]

Re:Python 3.9 by nemetroid on Tuesday October 20, 2020 @10:34AM (#24837767)

> If it was very widely used this bug probably would've been caught

As the top-level comment says, it rarely causes crashes.

[ Parent | on HN ]