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

pip install --fail-on-missing-deps #3261

Closed
anntzer opened this issue Nov 23, 2015 · 3 comments
Closed

pip install --fail-on-missing-deps #3261

anntzer opened this issue Nov 23, 2015 · 3 comments
Labels
auto-locked Outdated issues that have been locked by automation type: enhancement Improvements to functionality

Comments

@anntzer
Copy link
Contributor

anntzer commented Nov 23, 2015

I'd like to suggest a flag that would prevent installation of any dependencies (like --no-deps) and fail if any dependency is missing (printing out the list of missing dependencies).

Use case: environments when most packages should be installed via another package manager, e.g. conda or $linuxdistro-packagemanager and some package is not available for that package manager, but I'd still like to install whichever dependencies I can using it.

@xavfernandez
Copy link
Member

A solution could be the use of --no-deps combined with a possible pip check cf #2492

@xavfernandez xavfernandez added the type: enhancement Improvements to functionality label Nov 26, 2015
@anntzer
Copy link
Contributor Author

anntzer commented Jun 15, 2016

While this may work, this would require a install first (possibly lengthy, if there are compiled modules), even though the information is actually available before the actual install step.
I guess this really means, though, that the missing tool is more something like pip show for not-installed packages.

@dstufft
Copy link
Member

dstufft commented Mar 30, 2017

I'm going to close this issue. While I recognize that there are some cases when this might be useful, I believe that the cases where this is useful are sufficiently in the minority that adding the additional overhead (both code and mental) of a new option is not something that we want to do to support it.

@dstufft dstufft closed this as completed Mar 30, 2017
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: enhancement Improvements to functionality
Projects
None yet
Development

No branches or pull requests

3 participants