Hirokazu Yamamoto  committed e49cd4f

Merged revisions 71554-71555 via svnmerge from

r71554 | hirokazu.yamamoto | 2009-04-13 10:07:06 +0900 | 1 line

Fixed typo. (email.Utils => email.utils)
r71555 | hirokazu.yamamoto | 2009-04-13 10:21:56 +0900 | 1 line

Fixed another typos. (email.Utils => email.utils)

  • Participants
  • Parent commits 12a8d19
  • Branches 2.6

Comments (0)

Files changed (1)

File Doc/library/email.message.rst

       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
       does not have a ``filename`` parameter, this method falls back to looking
       for the ``name`` parameter.  If neither is found, or the header is
       missing, then *failobj* is returned.  The returned string will always be
-      unquoted as per :meth:`Utils.unquote`.
+      unquoted as per :func:`email.utils.unquote`.
    .. method:: get_boundary([failobj])
       Return the value of the ``boundary`` parameter of the
       :mailheader:`Content-Type` header of the message, or *failobj* if either
       the header is missing, or has no ``boundary`` parameter.  The returned
-      string will always be unquoted as per :meth:`Utils.unquote`.
+      string will always be unquoted as per :func:`email.utils.unquote`.
    .. method:: set_boundary(boundary)