This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kbk
Recipients amaury.forgeotdarc, gvanrossum, kbk, mark
Date 2008-04-09.19:02:17
SpamBayes Score 0.03149508
Marked as misclassified No
Message-id <1207767738.27.0.497078886937.issue2221@psf.upfronthosting.co.za>
In-reply-to
Content
PyObject_CallMethod is actually returning a
non-NULL result for sys.std{out,err}, and 
PyErr_Clear() isn't being run in flush_io.

The problem is deeper.  PyErr is being
used during unexceptional processing in
typeobject.c:slot_tp_getattr_hook() to
indicate that PyObject_GenericGetAttr() failed
and the __getattr__ method (used in IDLE) 
should be called.

Perhaps PyErr should be preserved in
slot_tp_getattr_hook(), instead.  Is this 
possibly a potential 2.6 issue for some uses
of getattr?  Or is the current solution 'good 
enough'?

ref issue1400.
History
Date User Action Args
2008-04-09 19:02:18kbksetspambayes_score: 0.0314951 -> 0.03149508
recipients: + kbk, gvanrossum, amaury.forgeotdarc, mark
2008-04-09 19:02:18kbksetspambayes_score: 0.0314951 -> 0.0314951
messageid: <1207767738.27.0.497078886937.issue2221@psf.upfronthosting.co.za>
2008-04-09 19:02:17kbklinkissue2221 messages
2008-04-09 19:02:17kbkcreate