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 orsenthil
Recipients Walter.Woods, barry, hdiogenes, orsenthil, r.david.murray
Date 2010-05-01.15:44:07
SpamBayes Score 9.29746e-06
Marked as misclassified No
Message-id <1272728650.66.0.329146207677.issue8572@psf.upfronthosting.co.za>
In-reply-to
Content
It seems that 3.x behavior is correct. I am quoting a relevant section from rfc 2616.

"""
It MUST be possible to combine the multiple header fields into one "field-name: field-value" pair, without changing the semantics of the message, by appending each subsequent field-value to the first, each
separated by a comma.
"""

- Should we change the 2.x behavior then? (This can break apps, which might be depending upon the existing behavior of 2.x code)

Also, this bug is on default value, it fair to assume that the default might given as None, or a string and rarely as int. I don't see anyone would have passed it (correctly for current code) as list.

Why don't we handle it at email.message.Message's get_all method?
get_all is supposed to return a list or None.

Attaching a patch (which is almost David's first suggestion).
History
Date User Action Args
2010-05-01 15:44:11orsenthilsetrecipients: + orsenthil, barry, hdiogenes, r.david.murray, Walter.Woods
2010-05-01 15:44:10orsenthilsetmessageid: <1272728650.66.0.329146207677.issue8572@psf.upfronthosting.co.za>
2010-05-01 15:44:08orsenthillinkissue8572 messages
2010-05-01 15:44:08orsenthilcreate