Ofek Lev

Yes that is the intention 😄 > I could see other uses, such as a FFI tool that takes a description of a C interface and generates a Python file...

As currently implemented it would look like: ```toml [build-system] requires = ["hatchling", "scikit-build-core", "mypyc"] build-backend = "hatchling.build" [project] name = "example" version = "0.1.0" [[project.extensions.scikit-build]] src = "src1/CMakeLists.txt" [[project.extensions.scikit-build]] src...

1. `[[build-system.extensions]]` is much better! 2. A package can define an arbitrary number of extension builders https://ofek.dev/extensionlib/builders/#plugin-registration

> Am I correct in assuming that this is really just a replacement for [hatch_build.py](https://hatch.pypa.io/latest/plugins/builder/custom/)? No. The idea is for any PEP 517 backend to be able to do 2...

> effectively need to wait for the community of PEP 517 backends to mature No. Anything that compiles or generates stuff with the intention of being placed in a wheel...

That's out of scope. This is purely for things that can build extensions to define their logic and communicate where files are/should be distributed.

This needs to be coupled with [conditional execution](https://ofek.dev/extensionlib/runners/#enabling) so not running a hook also prevents installing the required dependencies.

Sorry about that! I'll improve documentation but when you don't use the recommended installation mechanism file paths must be absolute.

Yes the easiest solution for that is to turn your scripts into a package. You can then either publish and install from PyPI or if private just build and point...

Nice!