Henry Schreiner
Henry Schreiner
I think it should be a platform, so it would never being enabled by default, you’d have to ask for that platform. Currently, wheels have to target a specific version,...
Yes, environments are pinned by cibuildwheel version (unless you request otherwise, via https://cibuildwheel.readthedocs.io/en/stable/options/#dependency-versions ) How is numpy pinning cibuildwheel if you are building it?
As for the build frontend, I'd say ideally make it a warning or even an error if a user specifically sets it to `pip`, but no warning/error if it's unset,...
You can, not good for a general composite action (since it affects the environment), but fine for workflows.
Where did I say that? That sounds reversed from what I was told by @charliermarsh and I think I always put it, the formatter is guaranteed to not introduce new...
FYI, `--exit-non-zero-on-fix` in the checker isn't required in pre-commit; pre-commit checks for changed files.
Yes, a non-zero exit code has always only been required if there were no file changes.
They only flip-flopped on it while developing it, and it seems to be quite stable now and documented in their help pages.
Pip would prefer to remove the `wheel` subcommand AFIAK, and has refused adding a matching `sdist` command. I think `uv build --wheel` (along with `uv build --sdist` and `uv build`,...
But it doesn’t actually put wheels in the wheelhouse if there’s already a built wheel, IIRC? Pip download will get everything you need then you can loop over any SDists...