[Python-Dev] unicode Exception messages in py2.7

Chris Barker chris.barker at noaa.gov
Fri Nov 15 01:02:17 CET 2013

On Thu, Nov 14, 2013 at 1:55 PM, Tres Seaver <tseaver at palladion.com> wrote:

> Fixing any bug is "changing behavior";  2.7 is not frozen for bugfixes.

Thank you.

> The real question is whether third-party code will break when the
> now-empty error messages appear with '?' littered through them?

right -- any bugfix changes behaviour, and any that can break any test
or code that is expecting (or working around) that behavior. So the
key question here is are there many (any?) tests or function code out
there that are counting on an empty message if and only if there
happens to be a non-ascii charactor in an assigned message.

It's hard for me to imagine that that's a common thing to test for,
but then I'm been known to lack imagination ;-)

> About the only things I can think of which might break would be doctests,
> but people *expect* those to break across third-dot releases of Python
> (one reason why I hate them).  Exception repr is explicitly *not* part of
> any backward-compatibility guarantees in Python.  Or code which
> explicitly works around the breakage could fail (urlparse changes between
> 2.7.3 and 2.7.4, anyone?d(

Sounds do-able to me, then...



Christopher Barker, Ph.D.

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov

More information about the Python-Dev mailing list