Closed adrianeboyd closed 1 year ago
It's brittle, but there's no pip API, and in the worst case it just doesn't warn.
I'm trying to think of the case where people definitely want the requirements to be checked and they might otherwise keep running into silent failures.
None of this is great.
If we worry about either scenario, we should still consider hooking up the skip_requirements_check
and allow users to control this behaviour. It doesn't make things more complex for users who don't use/need the flag.
I might be more tempted to just throw it out with the transition to weasel
.
I think we could say that we're removing this because pkg_resources
is deprecated and that would be okay.
Honestly I don't care strongly either way Adriane.
Then I'll remove it. It never really worked 100% properly anyway.
Replaced by #49.
Description
Replace deprecated
pkg_resources
with minimal handling of the output ofpip install --dry-run
in cases where packages need to be installed (depends on the text output ofpip install
) or the requirements contain conflicts or other errors (depends on the return code ofpip install
).Types of change
?
Checklist