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, kbandla, r.david.murray
Date 2013-06-05.14:26:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
My preliminary thought (and I haven't checked the code yet to make sure this will actually work), is that under the new email policies we are dealing with full-blown header objects, meaning that they can know the header name they represent.  This should theoretically make it possible to have a 'create header' function to create a header object (there may be one's been way too long since I've worked on this code) and then have:

  message[:0] = [my_new_header]

do the right thing.  As well as all the other list methods working as expected.  We'd also want a 'find_header' method that takes the header name and returns the index of the header in the list.

But, as I say, this is just a preliminary thought, it needs careful consideration before we decide to actually do something.
Date User Action Args
2013-06-05 14:26:38r.david.murraysetrecipients: + r.david.murray, barry, kbandla
2013-06-05 14:26:38r.david.murraysetmessageid: <>
2013-06-05 14:26:38r.david.murraylinkissue18139 messages
2013-06-05 14:26:38r.david.murraycreate