[issue634412] RFC 2387 in email package

Abhilash Raj added the comment: David: What about his API then? https://gist.github.com/maxking/b3ed4f54674e5f480275 Here cids are generated behind the scenes when the html part is added and those cids are assigned to the attachments on the first come basis? Like {0} is replaced by the cid

[issue634412] RFC 2387 in email package

R. David Murray added the comment: 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 anythi

[issue634412] RFC 2387 in email package

Abhilash Raj added the comment: David: How does this API look? https://gist.github.com/maxking/2f37bae7875dde027e3c -- ___ Python tracker ___ _

[issue634412] RFC 2387 in email package

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue634412] RFC 2387 in email package

R. David Murray added the comment: No, there is no requirement that attachment names be unique, and in fact no requirement that attachments (inline attachments, which is mostly what we are dealing with for 'related') have names at all. I have seen messages in the wild that had more than one a

[issue634412] RFC 2387 in email package

Abhilash Raj added the comment: Will the building of that 'dict' really be that difficult? Can we not walk over all the attachments and simply map cid to name of the attachment? All attachments have to have different names if I am right? -- ___ Pyth

[issue634412] RFC 2387 in email package

R. David Murray added the comment: My idea (which I haven't worked out in detail) is to add either a new content manager that extends raw_data_manager, or just add to raw_data_manager, a handler for 'multipart/related'. The set handler would handle a value of type 'dict', and expect it to con

[issue634412] RFC 2387 in email package

Abhilash Raj added the comment: David: I had a look at the examples and documentation as you said. I found some support for multipart/related in the form of `add_related` and `set_related` methods. But I am still confused on how to make content_manager recognize miltipart/related messages. Do

[issue634412] RFC 2387 in email package

Changes by R. David Murray : -- versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue634412] RFC 2387 in email package

R. David Murray added the comment: There is some support for this in the new email policies. Take a look at the new examples in the 3.4 email documentation in particular. The additional thing I would like to see is support in the content manager that recognizes multipart/related and makes it

[issue634412] RFC 2387 in email package

Abhilash Raj added the comment: I would like to work on this issue, but I would need a little help to start working on this feature. -- nosy: +abhilash.raj ___ Python tracker _

[issue634412] RFC 2387 in email package

Changes by A.M. Kuchling : -- keywords: -easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue634412] RFC 2387 in email package

R. David Murray added the comment: http://tools.ietf.org/html/rfc2387 has obsoleted 2112. -- title: RFC 2112 in email package -> RFC 2387 in email package versions: +Python 3.4 -Python 3.3 ___ Python tracker _