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 abhilash.raj, ajaksu2, barry, christian.heimes, etiffany, martin.panter, moijes12, r.david.murray
Date 2014-06-11.20:56:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402520184.05.0.755646712941.issue634412@psf.upfronthosting.co.za>
In-reply-to
Content
It is a clever idea, and might be worth considering, but it doesn't feel natural to have to specify the attachments before the html.  What I'd really like is an API that hides the messy details of the RFC from the library user, and I haven't thought of anything I'm satisfied with yet.  Specifically, it would be great if the 'keys' could be specially formatted strings ("@mypicid1@" or something like that) and the helper would automatically replace them with cids in both the html and the attachments.

It would probably be worth taking this discussion to the email-sig mailing list.
History
Date User Action Args
2014-06-11 20:56:24r.david.murraysetrecipients: + r.david.murray, barry, christian.heimes, ajaksu2, etiffany, martin.panter, moijes12, abhilash.raj
2014-06-11 20:56:24r.david.murraysetmessageid: <1402520184.05.0.755646712941.issue634412@psf.upfronthosting.co.za>
2014-06-11 20:56:24r.david.murraylinkissue634412 messages
2014-06-11 20:56:23r.david.murraycreate