[issue5951] email.message : get_payload args's documentation is confusing

Georg Brandl added the comment: Will be fixed along with all other such instances. -- resolution: -> postponed status: open -> closed ___ Python tracker ___

[issue5951] email.message : get_payload args's documentation is confusing

R. David Murray added the comment: No fault of yours, it's a real doc bug. I've been programming in python since 1997 or so, and I had to read the source code to figure it out when I went to use get_payload a couple months ago. That's why your bug report caught my eye. And even then I misreme

[issue5951] email.message : get_payload args's documentation is confusing

Loic Jaquemet added the comment: Ok, I understand. Thx + -> I need to learn python :/ -- ___ Python tracker ___ ___ Python-bugs-list

[issue5951] email.message : get_payload args's documentation is confusing

R. David Murray added the comment: The answer is that you do msg.get_payload(decode=True). The doc needs to be changed over to use keyword argument specification syntax, which I think would make that obvious. -- nosy: +r.david.murray versions: -Python 2.4, Python 2.5

[issue5951] email.message : get_payload args's documentation is confusing

Changes by jal : -- versions: +Python 2.4, Python 2.5, Python 2.7, Python 3.0, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list m

[issue5951] email.message : get_payload args's documentation is confusing

New submission from jal : >From documentation : http://docs.python.org/library/email.message.html?highlight=email#email.message.Message.get_payload get_payload([i[, decode]]) "With optional argument i,[..] If the payload is a string (i.e. is_multipart() is False) and i is given, a TypeError is