R. David Murray added the comment: Yes on 3.3 fixes, but you are right that it doesn't need fixed there. This appears to be a 3.4 regression. I used exactly the test you suggest to reproduce it on 3.4...there there is a chained traceback and Done does not get printed. So, the original report is indeed invalid, but we've uncovered a regression. Fortunately it is a low impact regression.
I'm guessing this arises from the improvements you made to the "fallback" logging of these errors. ---------- keywords: +3.4regression resolution: invalid -> status: closed -> open title: LogRecord.__init__ should handle exception if % operation fails -> Logging of logging exceptions can fail in 3.4 if args are unprintable versions: -Python 2.7, Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20918> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
