We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I want to create requirements.txt.
requirements.txt
I run pip-compile --output-file=requirements.txt requirements.in for the first time in my life and there is too much output.
pip-compile --output-file=requirements.txt requirements.in
This is confusing, because the output looks like a requirements file. Thus I think "the --output-file argument was ignored".
Is there a need for so much output?
I like to run the command and get one line of output. Output like
requirements.txt was created
An alternative solution would be to create no output.
First-time user experience is important.
If you agree, then I can write a pull-request for this change.
But first I would like to know if you want the change.
The text was updated successfully, but these errors were encountered:
You might find the -q argument helpful.
-q
Sorry, something went wrong.
No branches or pull requests
What's the problem this feature will solve?
I want to create
requirements.txt
.I run
pip-compile --output-file=requirements.txt requirements.in
for the first time in my life and there is too much output.This is confusing, because the output looks like a requirements file. Thus I think "the --output-file argument was ignored".
Is there a need for so much output?
Describe the solution you'd like
I like to run the command and get one line of output. Output like
Alternative Solutions
An alternative solution would be to create no output.
Additional context
First-time user experience is important.
If you agree, then I can write a pull-request for this change.
But first I would like to know if you want the change.
The text was updated successfully, but these errors were encountered: