A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2013-November/130201.html below:

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

[Python-Dev] unicode Exception messages in py2.7 [Python-Dev] unicode Exception messages in py2.7Steven D'Aprano steve at pearwood.info
Fri Nov 15 04:08:55 CET 2013
On Thu, Nov 14, 2013 at 04:02:17PM -0800, Chris Barker wrote:
> 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

It isn't clear that this is a bug at all.

Non-ascii Unicode strings are just a special case of the more general 
problem of what to do if printing the exception raises. If 
str(exception.message) raises, suppressing the message seems like a 
perfectly reasonable approach to me.



-- 
Steven
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4