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-compile should accept special files (pipes, fifo, pty, sockets, ...) as output files #2012
Comments
The main problem is that For example, setting |
Also the documentation should emphasize that |
Thanks for raising this issue, sounds like a reasonable request! I'll look into it. |
@manuco are you willing to contribute tests, at least? |
@webknjaz I'll have a look at it if it can help. Since those tests will be integrations tests (with the IOs of the OS), will they fit in the current tests ? |
@webknjaz Is this test ok for you ? |
Looks good, mostly. |
When running
pip-compile -o /dev/stdout
, the command blocks indefinitely. It shouldn't and should write the requirement file in the given file, even if it's not a bare file.Please note that
pip-compile | <other program>
doesn't work either (the other program doesn't receive anything).Please also note that
stderr
is cluttered by some eventual warnings not parseable by pip and is so not usable as a viable content source.Environment Versions
Steps to replicate
git clone <your favourite "using setup.py" project> && cd in
pip-compile setup.py -o /dev/stdout
Expected result
output on stdout (not stderr)
warnings (if any) on stderr
Actual result
<nothing and process blocked>
Steps to replicate (advanced)
TTY 1 :
mkfifo /tmp/mylovelyfifo
cat /tmp/mylovelyfifo
TTY 2 :
git clone <your favourite "using setup.py" project> && cd in
pip-compile setup.py -o /tmp/mylovelyfifo
Expected result
output on TTY 1
warnings (if any) on TTY 2
Actual result
<nothing and process blocked>
The text was updated successfully, but these errors were encountered: