-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
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
Improve build.util.project_wheel_metadata
#553
Comments
layday
pushed a commit
that referenced
this issue
Jan 25, 2023
) Co-authored-by: Henry Schreiner <[email protected]> Co-authored-by: layday <[email protected]> Closes #553
4 tasks
hmpf
added a commit
to hmpf/Argus
that referenced
this issue
Feb 8, 2024
While `tox` doesn't need to be in the venv, it DOES currently need to be less than version 4. `build` is useful for debugging pip errors and pip-compile trouble. Whenever pip-compile (via `tox -e upgrade-deps` for instance) fails with Backend subprocess exited when trying to invoke get_requires_for_build_wheel Failed to parse /PATH/pyproject.toml run `python -m build -w` to se what `build` is actually complaining about. See also pypa/build#553
hmpf
added a commit
to hmpf/Argus
that referenced
this issue
Feb 9, 2024
While `tox` doesn't need to be in the venv, it DOES currently need to be less than version 4. `build` is useful for debugging pip errors and pip-compile trouble. Whenever pip-compile (via `tox -e upgrade-deps` for instance) fails with Backend subprocess exited when trying to invoke get_requires_for_build_wheel Failed to parse /PATH/pyproject.toml run `python -m build -w` to see what `build` is actually complaining about. See also pypa/build#553
hmpf
added a commit
to Uninett/Argus
that referenced
this issue
Feb 9, 2024
While `tox` doesn't need to be in the venv, it DOES currently need to be less than version 4. `build` is useful for debugging pip errors and pip-compile trouble. Whenever pip-compile (via `tox -e upgrade-deps` for instance) fails with Backend subprocess exited when trying to invoke get_requires_for_build_wheel Failed to parse /PATH/pyproject.toml run `python -m build -w` to see what `build` is actually complaining about. See also pypa/build#553
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's the problem this feature will solve?
Currently, pip-tools uses
project_wheel_metadata()
to parse setup files and get install requirements of a package. The issue is that the function suppresses any errors if a setup file (or pyproject.toml) is invalid. See the example below.Example
That's because
project_wheel_metadata
usespep517.quiet_subprocess_runner
under the hood which suppresses the output.Describe the solution you'd like
It would be nice to have a parameter to control which runner will be used. A few options:
project_wheel_metadata(srcdir, isolated, quiet=false)
- will be usedpep517.default_subprocess_runner
project_wheel_metadata(srcdir, isolated, runner=pep517default_subprocess_runner
- pass a runner directlyExample
Additional context
The text was updated successfully, but these errors were encountered: