layday
layday
This is an oversight but a fortunate one, because fixing it would break passing config settings to setuptools' sdists and wheels :(
setuptools only accepts `--global-option`. This is passed to every hook invoked from build, so that an option that is valid for e.g. `build_wheel` (`python setup.py bdist_wheel`) is invalid for `get_requires_for_build_wheel`...
See https://github.com/pypa/build/issues/482.
I don't understand why we need to ditch pep517 to make the API thread-safe, can you explain?
We just have to pass some env vars I thought to the runner - all we'd have to do is make sure we're wrapping the pep517/user-provided runners.
I suppose we could set `PIP_USER` to `0` or pass `--no-user` to every pip command that we issue, if this is something that we want to handle in `build`.
build is not an "end user" in this context.
I don't think that build should be able to delete files or folders it might not have created itself. If the impetus for clearing `dist` out is that you're running...
The setuptools backend is found at `setuptools.build_meta`, not `setuptools.build.meta`
Maybe, but I think most people copy the backend config section from documentation.