> Imagine how Open Source Software could improve if a consortium of nations put their money and resources into commissioning bug fixes and enhancements, which would be of collective benefit.
This is the business model of Quansight Labs, whose employees help maintain much of the scientific python stack. Mostly tech companies, not governments, sponsoring the work
It sounds like their point is that there's precedent for things in early stages only being provided as source, with binary releases coming later when things are more stable
I think part of the point is that it doesn’t matter. You can’t preach “frugality” and @we all need to pitch in” and then use private jets and rock concerts for the few at the top. It is hypocritical.
We try to keep around useful versions of Python3, based on what wheels packagers make available. NumPy<2 provides PyPy3.9 wheels, and we have PyPy3.10 ready. Now that NumPy has moved to PyPy3.10 wheels, we will probably drop 3.9. Help is needed to move forward to 3.11/3.12.
The article is more about how to pin to prevent breakage, but also includes a link to the migration guide. A draft of the complete changeset is https://numpy.org/devdocs/release/2.0.0-notes.html. The changes move NumPy closer to the Python array API standard https://data-apis.org/array-api/latest/ which lays out a common, agreed-upon interfaces for tensor/array processing libraries.
This is the business model of Quansight Labs, whose employees help maintain much of the scientific python stack. Mostly tech companies, not governments, sponsoring the work