From 3bd4058d829500f1a91a4c317824fdc9bc41d393 Mon Sep 17 00:00:00 2001 From: Hirokazu Yamamoto Date: Mon, 13 Apr 2009 01:07:06 +0000 Subject: [PATCH] Fixed typo. (email.Utils => email.utils) --- Doc/library/email.message.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/library/email.message.rst b/Doc/library/email.message.rst index f2a78e1211..a10d716020 100644 --- a/Doc/library/email.message.rst +++ b/Doc/library/email.message.rst @@ -373,13 +373,13 @@ Here are the methods of the :class:`Message` class: If your application doesn't care whether the parameter was encoded as in :rfc:`2231`, you can collapse the parameter value by calling - :func:`email.Utils.collapse_rfc2231_value`, passing in the return value + :func:`email.utils.collapse_rfc2231_value`, passing in the return value from :meth:`get_param`. This will return a suitably decoded Unicode string whn the value is a tuple, or the original string unquoted if it isn't. For example:: rawparam = msg.get_param('foo') - param = email.Utils.collapse_rfc2231_value(rawparam) + param = email.utils.collapse_rfc2231_value(rawparam) In any case, the parameter value (either the returned string, or the ``VALUE`` item in the 3-tuple) is always unquoted, unless *unquote* is set -- 2.50.1