Open segevfiner opened 1 year ago
scikit-build-core
is ultimately planning on implementing a Hatch build plugin for this purpose
Until this issue is addressed, it would be nice for hatch new --init
to warn/error if the original project uses extension modules. Would have saved me some time exploring why hatch cheerfully created a broken package.
warn/error if the original project uses extension modules
Good idea, will do!
Of note: there is now an experimental hatch plugin for scikit-build-core!
Scikit-build-core looks really powerful, but also really overwhelming. Is there some simple way to migrate to Hatch if using a Cython extension via setuptools.Extension
given that I don't know anything about CMake?
Example: pytensor
no, but that's coming by the end of the year, I'm busy currently
oh you just need Cython support, yeah that already exists https://github.com/joshua-auchincloss/hatch-cython
A common problem with the new build tools is that they don't seem to support extension modules. This is often a blocker for projects to migrate to those new tools from setuptools. It would be nice to have proper and full support for this. Along the way, stuff like building such modules using CMake instead of a custom build system (A-la scikit-build) could be helpful so that more complex extension module could be built more easily.