doesn't respect unix pipes

[shanemikel]

try reproducing the problem with this:
pip list | head

[dstufft]

What do you mean "doesn't respect unix pipes", it doesn't have any control over them- it just uses stdout and stderr.

[shanemikel]

Most programs are written to expect that their pipes can be closed at any time, where they have to decide to continue to run (without writing to the nonexistent pipe) or die depending on whether or not they're doing something aside from providing the user with information. If you run the example above, you should see pip give exception.

[rbtcollins]

So you mean 'when pip can't write to stdout, it errors'. This seems reasonable: nohup pip is there for a reason :).

[dstufft]

I don't have a problem with just not printing output if there isn't a stdout/stderr to print too (or it's closed). PRs accepted!

[xavfernandez]

Closing this in favor of #4170 which contains more infos.