[ python-Bugs-854102 ] Message.get_filename() problem
SourceForge.net
noreply at sourceforge.net
Sat Oct 2 23:04:14 CEST 2004
Bugs item #854102, was opened at 2003-12-04 10:26
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=854102&group_id=5470
Category: Python Library
Group: Python 2.4
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Ervin Németh (nemethe)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: Message.get_filename() problem
Initial Comment:
There are obviously e-mails with non-standard encodings
(who wants to join me hating pine?)
See attached backtrace.
A local patch of
- return unicode(newvalue[2], newvalue[0] or
'us-ascii')
+ try:
+ return unicode(newvalue[2],
newvalue[0] or 'us-ascii')
+ except LookupError:
+ return unicode(newvalue[2],
'us-ascii', 'replace')
solved the problem here.
----------------------------------------------------------------------
>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2004-10-02 17:04
Message:
Logged In: YES
user_id=12800
This will be fixed in email 3.0/Python 2.4.
----------------------------------------------------------------------
Comment By: Ervin Németh (nemethe)
Date: 2004-05-12 10:28
Message:
Logged In: YES
user_id=768522
Barry, sorry but it is 6 month since the report. The mail
causing the problem is long lost.
You could try contacting Gregor Maier who commented on
mailman bug 803729 recently. He is at
http://sourceforge.net/users/maiergre/
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2004-05-10 10:50
Message:
Logged In: YES
user_id=12800
Please attach a sample test case to illustrate the problem.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=854102&group_id=5470
More information about the Python-bugs-list
mailing list