如果我与joblib并行启动一个进程,该进程使用unix管道(sed | uniq | blabla
)调用子进程,那么许多进程在使用Ctrl-C成功退出python进程后会向终端写入错误消息。 / p>
sed: couldn't write 13 items to stdout: Broken pipe
uniq: write error: Broken pipe
uniq: write error: Broken pipe
sed: couldn't flush stdout: Broken pipe
sed: couldn't flush stdout: Broken pipe
sed: couldn't write 1 item to stdout: Broken pipe
有没有办法使用joblib Parallel来避免输出如上所述?