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 rgbecker
Recipients BreamoreBoy, ajaksu2, jhylton, rgbecker, wam
Date 2014-07-19.13:10:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1405775411.72.0.864492387147.issue1047397@psf.upfronthosting.co.za>
In-reply-to
Content
I'll repeat the post I made to BreamoreBoy regarding this bug:

"re: http://bugs.python.org/issue1047397

this bug is now 10 years old. I'm not sure why it's to be considered
closed because the original intent of the bug report was that the html
output of the cgitb module could be confused and errors during
evaluation could make the html output fail. So far as I can tell by
modifying the original cgitbbug.py to run under python 3.4.1 it still
fails to correctly produce html when a bug occurs in cgitb.html.
Producing a more reasonable traceback is certainly a step forward, but
I think that has been true since at least 3.1. The whole point of
cgitb is to produce something reasonable for an html consumer."

I have re-created the original 002 patch with mods for python 3.4.1. It's a bit of a shame that this wasn't fixed 10 years ago. Hopefully any style pedants will find this patch more acceptable. Personally I don't think style errors should prevent a working fix from being adopted. I would have just fixed the fix style and carped afterwards.
History
Date User Action Args
2014-07-19 13:10:11rgbeckersetrecipients: + rgbecker, jhylton, ajaksu2, BreamoreBoy, wam
2014-07-19 13:10:11rgbeckersetmessageid: <1405775411.72.0.864492387147.issue1047397@psf.upfronthosting.co.za>
2014-07-19 13:10:11rgbeckerlinkissue1047397 messages
2014-07-19 13:10:11rgbeckercreate