Changes by Josh Lee jlee...@gmail.com:
--
nosy: +jleedev
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13444
___
___
Python-bugs-list mailing list
Martin Panter added the comment:
Shouldn’t this issue be marked closed and fixed?
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13444
___
Changes by Berker Peksag berker.pek...@gmail.com:
--
resolution: - fixed
stage: needs patch - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13444
___
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 150e096095e5 by Antoine Pitrou in branch '3.2':
Issue #13444: When stdout has been closed explicitly, we should not attempt to
flush it at shutdown and print an error.
http://hg.python.org/cpython/rev/150e096095e5
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13444
___
Ronny Pfannschmidt ronny.pfannschm...@gmail.com added the comment:
i think checking for closed is the correct solution
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13444
___
Antoine Pitrou pit...@free.fr added the comment:
I think closing stdout is a legitimate desire so, yes, I would consider it a
bug if we print an error in that case.
A patch could either first check the closed attribute, or silence the
ValueError.
--
stage: - needs patch
type: -
New submission from Ronny Pfannschmidt ronny.pfannschm...@gmail.com:
not sure if this is to be considered a bug,
but python3.2 tries to flush sys.stdout on shutdown, even if its closed
$ python3.2 -c 'import sys;sys.stdout.close()'
Exception ValueError: 'I/O operation on closed file.' in
