[New-bugs-announce] [issue5321] I/O error during one-liner gives no (!) diagnostic (and fails to return OS error status)

Mike Coleman report at bugs.python.org
Thu Feb 19 18:50:04 CET 2009


New submission from Mike Coleman <mkc at users.sourceforge.net>:

$ python3.0 -c 'print((1, 2, 3))' > /dev/full || echo error status
$

This command gives no indication whatsoever that anything has gone
wrong.  Following this with strace demonstrates that the interpreter is
in fact ignoring these errors:

2589  write(1, "(1, 2, 3)\n"..., 10)    = -1 ENOSPC (No space left on
device)
2589  rt_sigaction(SIGINT, {SIG_DFL}, {0x47aa49, [], SA_RESTORER,
0x7fd5aa9da080}, 8) = 0
2589  write(1, "(1, 2, 3)\n"..., 10)    = -1 ENOSPC (No space left on
device)
2589  write(1, "(1, 2, 3)\n"..., 10)    = -1 ENOSPC (No space left on
device)
2589  write(1, "(1, 2, 3)\n"..., 10)    = -1 ENOSPC (No space left on
device)
2589  exit_group(0)                     = ?

----------
components: Interpreter Core
messages: 82486
nosy: mkc
severity: normal
status: open
title: I/O error during one-liner gives no (!) diagnostic (and fails to return OS error status)
type: behavior
versions: Python 3.0

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5321>
_______________________________________


More information about the New-bugs-announce mailing list