Skip to content
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

More visible error on broken inputs #112

Open
jaraco opened this issue Aug 5, 2024 · 0 comments
Open

More visible error on broken inputs #112

jaraco opened this issue Aug 5, 2024 · 0 comments

Comments

@jaraco
Copy link
Owner

jaraco commented Aug 5, 2024

Currently, pip-run is very lenient about reading dependencies. It does so because it aims to be generous about what inputs it reads for requirements, so wants to ignore invalid ones.

However, as projects like coherent.build start using this functionality for the build backend metadata discovery, silently ignoring subtle errors makes it difficult to troubleshoot. Take coherent-oss/coherent.build#17 as an example.

Probably, the dependency reader should suppress select errors and conditions that are known to be ignorable, but allow others to bubble up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant