Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, christian.heimes, gvanrossum, r37c
Date 2008-01-07.18:18:53
SpamBayes Score 0.00165865
Marked as misclassified No
Message-id <1199729934.87.0.0247510023221.issue1754@psf.upfronthosting.co.za>
In-reply-to
Content
I think this is not possible if we want to preserve compatibility; at
least, str(e.strerror) must not fail.

I can see different solutions:
1) Don't fix, and upgrade to python 3.0
2) Store an additional e.unicodeerror member, use it in a new
EnvironmentError.__unicode__ method, and call this from PyErr_Display.
3) Force FormatMessage to return US-English messages.

My preferred being 1): python2.5 is mostly encoding-naive, python3 is
unicode aware, and I am not sure we want python2.6 contain both code.
Other opinions?
History
Date User Action Args
2008-01-07 18:18:54amaury.forgeotdarcsetspambayes_score: 0.00165865 -> 0.00165865
recipients: + amaury.forgeotdarc, gvanrossum, christian.heimes, r37c
2008-01-07 18:18:54amaury.forgeotdarcsetspambayes_score: 0.00165865 -> 0.00165865
messageid: <1199729934.87.0.0247510023221.issue1754@psf.upfronthosting.co.za>
2008-01-07 18:18:53amaury.forgeotdarclinkissue1754 messages
2008-01-07 18:18:53amaury.forgeotdarccreate