Senthil Kumaran <orsent...@gmail.com> added the comment: 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). ---------- keywords: +patch Added file: http://bugs.python.org/file17165/issue8572.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8572> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
