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 ncoghlan
Recipients barry, cvrebert, exarkun, ezio.melotti, ncoghlan, pitrou
Date 2009-12-13.01:09:43
SpamBayes Score 2.3171574e-06
Marked as misclassified No
Message-id <1260666586.49.0.183979596221.issue6108@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2009-12-13 01:09:47ncoghlansetrecipients: + ncoghlan, barry, exarkun, pitrou, ezio.melotti, cvrebert
2009-12-13 01:09:46ncoghlansetmessageid: <1260666586.49.0.183979596221.issue6108@psf.upfronthosting.co.za>
2009-12-13 01:09:45ncoghlanlinkissue6108 messages
2009-12-13 01:09:43ncoghlancreate