Nick Coghlan <ncogh...@gmail.com> added the comment: Following this down the rabbit hole a little further: Issue #2517 (the origin of my checkin) was just a restoration of the __unicode__ slot implementation that had been ripped out in r51837 due to Issue #1551432.
At the time of the r64791 checkin, BaseException_str and BaseException_unicode were identical aside from the type of object returned (checking SVN head shows they're actually still identical). However, it looks like several exceptions with __str__ overrides (i.e. Unicode[Encode/Decode/Translate]Error_str, EnvironmentError_str, WindowsError_str. SyntaxError_str, KeyError_str) are missing corresponding __unicode__ overrides, so invoking unicode() on them falls back to the BaseException_unicode implementation instead of using the custom formatting behaviour of the subclass. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6108> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
