Issue 5320: I/O error during one-liner gives bad diagnostic (and fails to return OS error status) (original) (raw)
Issue5320
Created on 2009-02-19 17:45 by mkc, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (3) | ||
|---|---|---|
| msg82485 - (view) | Author: Mike Coleman (mkc) | Date: 2009-02-19 17:45 |
| $ python2.6 -c 'print 1, 2, 3' > /dev/full | | echo error status close failed in file object destructor: Error in sys.excepthook: Original exception was: $ It seems like something other than blank lines should be printed here. | |
| msg82487 - (view) | Author: Mike Coleman (mkc) | Date: 2009-02-19 17:52 |
| Also, as with the other python versions, notice that the error status is EXIT_SUCCESS (which it should not be). | ||
| msg112343 - (view) | Author: Georg Brandl (georg.brandl) *  |
Date: 2010-08-01 15:07 |
| I think this can be merged with #5319. |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:45 | admin | set | github: 49570 |
| 2010-08-01 15:07:10 | georg.brandl | set | status: open -> closednosy: + georg.brandlmessages: + superseder: stdout error at interpreter shutdown fails to return OS error statusresolution: duplicate |
| 2009-02-19 17:52:12 | mkc | set | messages: + |
| 2009-02-19 17:45:14 | mkc | create |