Henry Schreiner

> You introduced uv to this repo. How can we get the compiler messages back during the package build? The latest versions of uv (from a day or two ago)...

Yes, you can add it to the .pre-commit-config.yaml file. See https://learn.scientific-python.org/development/guides/style/#type-checking. On the pyproject.tmol, this is shown in the scikit_build_core example, and new projects should really be using that instead,...

Going to get it in for the next version; as seen in the tests, you can work around the change if you need the old behavior using `__file__`.

You should never add an upper bounds to Requires-Python. Most packages don't know it until after they are released, and even for ones that know they won't support the next...

That is released now, so something like this works: ```ruby gem 'jekyll-sass-converter', '~> 3.1.0' ```

For the ninja comment: ninja is only requested if it's not on the system (or is too old). Otherwise you wouldn't be able to support all the platforms without wheels.

If uv didn't use a different random path every time, but cached the build environment, then that would be solved, I think. Might be something to look into? It would...

`scikit-build-core` works fine with build isolation. (and I’ll look into meson-python soon)

Just curious, have you tried using the Stable ABI? That would be a single binary instead one per Python version. The RC is out now, binaries are supposed to be...

Strong +1, I've been bit by this several times, such as with `cmake`, when I've made a broken release then couldn't fix the problem quickly and had to wait for...