Hi folks, My name is Sean and I'm the author of several GIS packages using Numpy: Fiona, Rasterio, and Shapely. I've followed Numpy's trail when it comes to wheel building for many years and now I'm seeking advice on how to prioritize platforms to support and how to pay for the labor and computing that it takes to build wheels and maintain the infrastructure over time. Fiona and Rasterio have an order of magnitude more C library dependencies than Numpy, via GDAL (https://gdal.org/), which is almost more of an OS than a library.
I found a thread in the archive about adding musllinux wheels, but it wasn't clear to me how the work gets done, who does, and how it gets paid for. Does NumFOCUS support pay a maintainer to do it? Are Numpy maintainers adding new platform builds as part of their day jobs? Are they donating their own time to the effort? Does the Numpy project aspire to provide wheels for all of the top N platforms? Is it more than an aspiration? Is support for one or more platforms part of any sponsorship agreement? Maybe users and sponsorship cover the cost of building wheels and maintenance entirely for Numpy, but it's not so in my case. I've got so many questions in this vein, and I'm grateful for any answers or insights or more discussion. Thanks! _______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
