We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When you run from inside a venv (in my case, a venv inside conda), then python -m build uninstalls setuptools after running python -m build.
python -m build
And then, on a second run, it immediately breaks, even with setuptools listed in the requires clause (assuming it is needed for ensurepip, perhaps?)
python3 -m venv venv . venv/bin/activate.fish python -m pip install build python -m build # setuptools is now gone python -m build ERROR Backend 'setuptools.build_meta' is not available
Probably closely related to #97 . I am in the same anaconda python3.7 env described in #108, only now with a "setuptools>=42" requirement.
The text was updated successfully, but these errors were encountered:
Yeah, sorry about that 😕
Can you try #99 and see if it fixes it for you? I will come back to it this month and try to get it finally merged.
Sorry, something went wrong.
This should no longer be the case with the new isolated build methods.
No branches or pull requests
When you run from inside a venv (in my case, a venv inside conda), then
python -m build
uninstalls setuptools after runningpython -m build
.And then, on a second run, it immediately breaks, even with setuptools listed in the requires clause (assuming it is needed for ensurepip, perhaps?)
Probably closely related to #97 . I am in the same anaconda python3.7 env described in #108, only now with a "setuptools>=42" requirement.
The text was updated successfully, but these errors were encountered: