Message 64793 - Python tracker

➜

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	benjamin.peterson
Recipients	amaury.forgeotdarc, benjamin.peterson, christoph
Date	2008-03-31.21:36:01
SpamBayes Score	0.025791407
Marked as misclassified	No
Message-id	<1206999362.71.0.318786121665.issue2517@psf.upfronthosting.co.za>
In-reply-to

Content
I am going to reopen this issue for Py3k. The recommended encoding for Python source files in 2.x is ASCII; I wouldn't say correctly dealing with non-ASCII exceptions is fully supported. In 3.x, however, the recommended encoding is UTF-8, so this should work. In Py3k, str(e) # str is unicode in Py3k does work correctly, and that'll have to be used because the message attribute is gone is 3.x. However, the problem Amaury pointed out is not fixed. Exceptions that cannot encoding into ASCII are silently not printed. I think a warning should at least be printed.

I am going to reopen this issue for Py3k. The recommended encoding for
Python source files in 2.x is ASCII; I wouldn't say correctly dealing
with non-ASCII exceptions is fully supported. In 3.x, however, the
recommended encoding is UTF-8, so this should work.

In Py3k,
str(e) # str is unicode in Py3k
does work correctly, and that'll have to be used because the message
attribute is gone is 3.x.
However, the problem Amaury pointed out is not fixed. Exceptions that
cannot encoding into ASCII are silently not printed. I think a warning
should at least be printed.

History
Date	User	Action	Args
2008-03-31 21:36:03	benjamin.peterson	set	spambayes_score: 0.0257914 -> 0.025791407 recipients: + benjamin.peterson, amaury.forgeotdarc, christoph
2008-03-31 21:36:02	benjamin.peterson	set	spambayes_score: 0.0257914 -> 0.0257914 messageid: <1206999362.71.0.318786121665.issue2517@psf.upfronthosting.co.za>
2008-03-31 21:36:01	benjamin.peterson	link	issue2517 messages
2008-03-31 21:36:01	benjamin.peterson	create