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.
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
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.
As the top-level comment says, it rarely causes crashes.
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.
I was just using the expit function from scipy yesterday by the way, because that's where it was implemented.