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 barry
Recipients barry, kbandla, r.david.murray, suryak
Date 2016-08-22.15:30:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I've updated this to Python 3.6, but I don't know if there's time to design an API and implementation in the time left before beta 1.  But a use case has come up, so I want to reboot this discussion (yes, it should go to email-sig too).

Apparently ARC headers <> requires a header order.  In Mailman we have a GSoC student who is working on an implementation, and he's stuck because he needs to *prepend* ARC headers on the message, but the API gives him no direct way to do this.

We do have all the API problems that RDM points out.  I'm not going to suggest to the student that they use Message._headers.  It seems like the only way to do what he needs is to .get() all the headers in order, then del them all, manipulate the list out-of-band, and then re-add them all in the original order with the ARC headers at the front.  Yuck.
Date User Action Args
2016-08-22 15:30:25barrysetrecipients: + barry, r.david.murray, kbandla, suryak
2016-08-22 15:30:25barrysetmessageid: <>
2016-08-22 15:30:25barrylinkissue18139 messages
2016-08-22 15:30:25barrycreate