I am working on an NSF proposal (summarized at Scikit Build Proposal - ISciNumPy) to work on scikit-build (KitWare’s official CMake adaptor for Python) over the next three years. Would the PyTorch developers be interested in being listed in that proposal? I could help with transitioning the manually maintained wrappers currently used by PyTorch as part of the funding for that work, ideally before distutils is removed from Python in version 3.12. It also would lightly cover continued maintenance of pybind11 and cibuildwheel; I’ve previously helped PyTorch with pybind11.
Feel free to move this If I posted it in the wrong place, “packaging” seemed right. The “about” is empty.
Sorry for the late reply, I have been away and it took some time to discuss this internally.
We would be happy to be listed in this proposal especially given the key role of CMake in our build . Having the right build system would definitely help us simplify a lot of our build system across different platform and configurations.
Also any project improving pybind11 is welcome as we use it more and more.
Don’t hesitate to contact me if you need a more detailed letter of support!
Would it be possible to get the following letter filled out Collaborator Letter - Google Docs by mid day tomorrow? Proposal is due tomorrow. It’s just a standard template, no extra text needed or even allowed.
I can add 1-3 sentences to the " Facilities, Equipment or Other Resources section" that says anything, I’d put unless told otherwise:
\item Letter from \textbf{<contact>, PyTorch (<affiliation>)}:
PyTorch uses a custom wrapper to drive a CMake build. Dr./Mr. <contact> will work
with us to replace the existing build process with scikit-build, and utilize the new configuration
files-in-Python-packages support planned for CMake. This will help simplify a lot of the build
system across different platform and configurations. We also welcome related
improvements to pybind11.
As you might know by now, the CSSI grant for scikit-build was successful. Work on scikit-build, focused on scikit-build-core, has started. It is going a bit slower than initially planned due to my involvement teaching a class at Princeton this semester, but we are at the point should start talking about it, sharing what we are doing, and taking input in what is needed to use scikit-build (specifically scikit-build-core) in projects!
We are planning to have community meetings on the third Friday of every month, starting November 18th, at 12:00 PM EST. Meeting (Google meet) is here: https://meet.google.com/dvx-jkai-xhq. Anyone interested is invited.
For our first meeting, I’ll have some slides prepared showing scikit-build-core, some of the features that were not possible before, and look at some initial PRs that adapt projects like awkward, cmake, and pybind11’s examples to us it. We’ll have a look at the design, and discuss some design decisions we are currently thinking about. We also will have a short update on scikit-build classic, and the planned migration path toward moving it to use core in 1.0. There will be some time for open discussion, as well.