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 r.david.murray
Recipients barry, r.david.murray, tseaver
Date 2010-04-05.20:03:34
SpamBayes Score 1.14268e-08
Marked as misclassified No
Message-id <>
Depending on the feature, I might agree with that, but I wasn't involved in that decision.

If email only supports something structured with proper MIME headers and multifile is more general (which I *think* is the case, but I haven't actually tried to run any tests to confirm it), does that mean we should have kept multifile in py3?  I'm inclined to say no.  Should we make email support the more general case?  I'll at least keep it in the back of my mind as I/we work on email6.

Multifile is still there in 2.7, at the moment.

I presume you have a use case for the multifile module.  Could you do me a favor and add that use case the set of use cases in the email wiki?
(  It would be a good idea to mention there that email is supposed to supersede multifile.
Date User Action Args
2010-04-05 20:03:35r.david.murraysetrecipients: + r.david.murray, barry, tseaver
2010-04-05 20:03:35r.david.murraysetmessageid: <>
2010-04-05 20:03:34r.david.murraylinkissue8318 messages
2010-04-05 20:03:34r.david.murraycreate