layday
layday
https://github.com/pypa/build/pull/632 mirrors the programmatic API by allowing users to pass config settings to each hook separately, which I think is an elegant, permanent way out of this impasse. I can...
> Personally, I think trying having some sort of heuristic to detect setuptools and setuptools-wrappers is good enough, and I think it's an acceptable tradeoff to not put out this...
> This is heavily used in scikit-build-core and meson-python. Fair enough, but perhaps owing to setuptools' relative popularity, most reported issues with config settings appear to concern setuptools. It's a...
setuptools will error if: * You pass `egg_info`-specific options to any hook other than `get_requires_for_build_*` * You pass `sdist`-specific options to any hook other than than `build_sdist` * You pass...
> Hmm, can't you just do something like this(when used in combination with #627) to ensure the option gets passed to the right setuptools command? ~~No, that won't work.~~ >...
I've been writing built dist filenames to a JSON file in the dist folder, but that ends up being picked up by twine with `dist/*`, which attempts to upload it...
How would I reproduce this in uv? It doesn't expose a build command.
Ah, but that’s for IPC with the build backend. pyproject-hooks works exactly the same way.
Closing for the same reason as #138.
Support for inline dicts was removed from Pyright in [June](https://github.com/microsoft/pyright/releases/tag/1.1.366), by the way, which seems rather unfortunate.