Robin Becker added the comment:

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.

----------
Added file: http://bugs.python.org/file35995/bugfix003.patch

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue1047397>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to