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 synx
Recipients akuchling, anthonybaxter, barry, benno37, jlgijsbers, synx
Date 2007-11-27.09:49:20
SpamBayes Score 0.4928047
Marked as misclassified No
Message-id <1196156961.77.0.715915253685.issue756982@psf.upfronthosting.co.za>
In-reply-to
Content
I dunno if this is helpful, but in the 2.5 module, it parses mailboxes
into rfc822 messages, but then expects them to be email.Message messages
when unparsing them back to a mailbox. mbox2.add(mbox1.popitem()[1])
fails with rfc822 as the default factory. Since the "factory" is the
only thing still using rfc822, it's easy to remove the use of rfc822
from this module entirely, which also eliminates the parsing/unparsing
disconnect.
Files
File name Uploaded
mailbox.py.patch synx, 2007-11-27.09:49:21
History
Date User Action Args
2007-11-27 09:49:22synxsetspambayes_score: 0.492805 -> 0.4928047
recipients: + synx, barry, akuchling, anthonybaxter, jlgijsbers, benno37
2007-11-27 09:49:21synxsetspambayes_score: 0.492805 -> 0.492805
messageid: <1196156961.77.0.715915253685.issue756982@psf.upfronthosting.co.za>
2007-11-27 09:49:21synxlinkissue756982 messages
2007-11-27 09:49:21synxcreate