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 codegrunt
Recipients codegrunt, exarkun, georg.brandl, jafo
Date 2008-01-19.14:01:26
SpamBayes Score 0.047490872
Marked as misclassified No
Message-id <1200751287.64.0.198668993193.issue1598083@psf.upfronthosting.co.za>
In-reply-to
Content
Surely it's not a good idea to attempt to generate an exception within
an exception handler, couldn't this lead to an infinite loop scenario?

The checks prior to fputs() handle any errors by calling err_closed()
and returning -1. I suggest we do the same for the fputs() statement.
According to the documentation for fputs(), any errors result in a
return value of EOF, therefore an if(fputs(...) == EOF) { ... } check
seems appropriate.

I enclose a patch to this end, please let me know whether I'm way off
the mark here :-)
History
Date User Action Args
2008-01-19 14:01:28codegruntsetspambayes_score: 0.0474909 -> 0.047490872
recipients: + codegrunt, georg.brandl, jafo, exarkun
2008-01-19 14:01:27codegruntsetspambayes_score: 0.0474909 -> 0.0474909
messageid: <1200751287.64.0.198668993193.issue1598083@psf.upfronthosting.co.za>
2008-01-19 14:01:26codegruntlinkissue1598083 messages
2008-01-19 14:01:26codegruntcreate