-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Review the usability of pip's command line API for calling from other processes #6099
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
Comments
#5400 <- sorta kinda relevant. |
One thing that I think is important for this is making it so that all log messages go to stderr instead of stdout. Currently, IIRC In cases where |
More machine-friendly output formats would help greatly. Currently have to scrape the human-readable logging output from subprocess stdout in |
As the officially supported means of using pip from your program is via its command line interface, we should consider whether our command line API is "automation friendly" in this sense.
Specific things we should look at:
--user
flag is a common culprit here, as it doesn't interact well with certain other options like--target
.At the moment, we have
--isolated
, but that's a bit of a sledgehammer option, requiring users to replicate pip's option-handling logic if they want to respect some config (for example, network settings) but not others (for example,--user
)Note that this would also help pip itself, in its test suite and in places like build environment creation.
I'm just adding this as a reminder that we should consider this use case. It may be that there's nothing that we actually need to do (except possibly provide some more detailed recommendations on "how to call pip from your application").
The text was updated successfully, but these errors were encountered: