➜

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.

classification
Title: Message.get_filename() problem
Type: Stage:
Components: Library (Lib) Versions: Python 2.4
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: barry Nosy List: barry, nemethe
Priority: normal Keywords:

Created on 2003-12-04 15:26 by nemethe, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
traceback.log nemethe, 2003-12-04 15:26 traceback
Messages (4)
msg19275 - (view) Author: Ervin Németh (nemethe) Date: 2003-12-04 15:26 
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.
msg19276 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2004-05-10 14:50 
Logged In: YES 
user_id=12800

Please attach a sample test case to illustrate the problem.
msg19277 - (view) Author: Ervin Németh (nemethe) Date: 2004-05-12 14:28 
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/
msg19278 - (view) Author: Barry A. Warsaw (barry) * (Python committer) Date: 2004-10-02 21:04 
Logged In: YES 
user_id=12800

This will be fixed in email 3.0/Python 2.4.
History
Date User Action Args
2022-04-11 14:56:01adminsetgithub: 39664
2003-12-04 15:26:46nemethecreate