From: SourceForge.net <no...@so...> - 2007-02-28 00:00:04
|
Bugs item #1670422, was opened at 2007-02-28 02:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1670422&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: hawking2 (hawking2) Assigned to: Nobody/Anonymous (nobody) Summary: archivemail python-2.5 fix Initial Comment: archivemail have problems running with python-2.5 Here is the traceback: hawking@mars:~ archivemail -d 5 .maildir/local Traceback (most recent call last): File "/usr/bin/archivemail", line 1469, in <module> main() File "/usr/bin/archivemail", line 687, in main archive(mailbox_path) File "/usr/bin/archivemail", line 1130, in archive _archive_dir(mailbox_name, final_archive_name, "maildir") File "/usr/bin/archivemail", line 1270, in _archive_dir add_status_headers(msg) File "/usr/bin/archivemail", line 809, in add_status_headers match = re.search(":2,(.+)$", message.fp.name) AttributeError: _ProxyFile instance has no attribute 'name' .maildir/local is a Maildir and message is a rfc822.Message instance. In python2.4 message.fp.name gives the path of the file where this message is stored. In python2.5 this doesn't exist but same info is avaliable from 'message.fp._file.name' I've written a patch for archivemail-0.7.0 to check for python version and decide whether to use message.fp.name or message.fp._file.name and the tool seems to work fine. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1670422&group_id=49630 |