The BrokenPipeError
is normal as said phantom because the reading process (head) terminates and closes its end of the pipe while the writing process (python) still tries to write.
Is is an abnormal condition, and the python scripts receives a BrokenPipeError
- more exactly, the Python interpreter receives a system SIGPIPE signal that it catches and raises the BrokenPipeError
to allow the script to process the error.
And you effectively can process the error, because in your last example, you only see a message saying that the exception was ignored - ok it is not true, but seems related to this open issue in Python : Python developpers think important to warn user of the abnormal condition.
What really happens is that AFAIK the python interpreter always signals this on stderr, even if you catch the exception. But you just have to close stderr before exiting to get rid of the message.
I slightly changed your script to :
- catch the error as you did in your last example
- catch either IOError (that I get in Python34 on Windows64) or BrokenPipeError (in Python 33 on FreeBSD 9.0) - and display a message for that
- display a custom Done message on stderr (stdout is closed due to the broken pipe)
- close stderr before exiting to get rid of the message
Here is the script I used :
import sys
try:
for i in range(4000):
print(i, flush=True)
except (BrokenPipeError, IOError):
print ('BrokenPipeError caught', file = sys.stderr)
print ('Done', file=sys.stderr)
sys.stderr.close()
and here the result of python3.3 pipe.py | head -10
:
0
1
2
3
4
5
6
7
8
9
BrokenPipeError caught
Done
If you do not want the extraneous messages just use :
import sys
try:
for i in range(4000):
print(i, flush=True)
except (BrokenPipeError, IOError):
pass
sys.stderr.close()
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…