[issue19485] Slightly incorrect doc for get_param method in Lib/email/message.py

R. David Murray added the comment: Thanks, Vajrasky. Looks like this was a cut and paste error when Barry updated the docs for 3.3, since it is correct in the 2.7 module. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed

[issue19485] Slightly incorrect doc for get_param method in Lib/email/message.py

Roundup Robot added the comment: New changeset c574951deadd by R David Murray in branch '3.3': #19485: clarify get_param example. http://hg.python.org/cpython/rev/c574951deadd New changeset e3180c58a78c by R David Murray in branch 'default': Merge #19485: clarify get_param example. http://hg.pyt

[issue19485] Slightly incorrect doc for get_param method in Lib/email/message.py

R. David Murray added the comment: Vajrasky: FYI, you can select the 'email' component for tickets like this, and I'll be automatically made nosy (as will Barry Warsaw). -- components: +email nosy: +barry type: -> behavior versions: +Python 2.7, Python 3.3

[issue19485] Slightly incorrect doc for get_param method in Lib/email/message.py

New submission from Vajrasky Kok: Lib/email/message.py, line 665 & 666: param = msg.get_param('foo') param = email.utils.collapse_rfc2231_value(rawparam) Where does rawparam come from? On top of that, sending the result of get_param to collapse_rfc2231_value can make it chokes if the

[issue19485] Slightly incorrect doc for get_param method in Lib/email/message.py

Changes by Vajrasky Kok : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail