Henry Schreiner

Side comment: `uv init --build-backend scikit` doesn't actually do anything different than `uv init`, there's no build backend without `--lib` or similar. Maybe that should be an error?

Do you have a MANIFEST.in? .pyx isn't included by setuptools by default, IIRC.

You don't have to do this if you use scikit-build-core. :) I'm not sure if uv needs/should document every quirk of every build backend and binding tool? Also, you don't...

FYI, here's the procedure for scikit-build-core: ```bash uv init --lib --build-backend scikit hello ``` pyproject.toml: ```toml [project] name = "hello" version = "0.1.0" description = "Add your description here" readme...

That's inclusion in the SDist, not wheel. Wheel inclusion is controlled by package data in setuptools.

This is the only failing part, don't know if it's directly pyodide's fault: ``` ______________________ test_NormalConstraint_bad_input_4 _______________________ def test_NormalConstraint_bad_input_4(): > with pytest.raises(ValueError, match="positive definite"): E Failed: DID NOT RAISE /home/runner/work/iminuit/iminuit/tests/test_cost.py:1573:...

I bet NumPy is compiled with exceptions turned off; maybe this function actually raises the exception from the compiled code? I'll look into this and report to pyodide with what...

If you haven't started using `uv`, you should try it, even if it's just `uv venv` and `uv pip`: ```console $ uv venv Using CPython 3.13.3 interpreter at: /usr/local/opt/[email protected]/bin/python3.13 Creating...

TL;DR: The fork supports older versions of Make vs. the official jobserver implementation, which requires a very new version. Once we don't care about older versions of Make, the fork...

1.13.0 is out. Leaving this open since 1.13.1 is not available in the fork yet.