Yes of course. The backend will want to use a library.
Say build(… a few facts about the package) and be ready to go.
I’ve updated the hook in pip and setuptools. It makes pip simpler which I think is great. Don’t worry about the
.pth file, now moved into setuptools’ part of the hook.
The naming of the parameters is a little awkward. I have passed the same
prepare_metadata_for_build_wheel. It is like the root of a wheel. It contains the
It is easier for setuptools to let the other hook take care of
*.dist-info which is always accomplished by bdist_wheel converting an
.egg-info directory. (Any number of setuptools metadata plugins write to egg-info during its build). We already caled the metadata hook to find dependencies before installing our editable distribution.
I tested this against pip’s test project
python -m pip install -e tests/data/packages/pep517_setup_and_pyproject/