Lines Matching refs:multipart

29 :mimetype:`multipart/\*` or :mimetype:`message/rfc822`.
49 documents such as :mimetype:`multipart/\*` and :mimetype:`message/rfc822`
138       "msg.get_content_maintype() == 'multipart'" will return the ``True``.
320       inside a :mimetype:`multipart/digest` container, in which case it would
342       :mimetype:`multipart/digest` containers.  Such subparts have a default
441       message is a :mimetype:`multipart`, then the list will contain one element
482       Here's an example that prints the MIME type of every part of a multipart
496          multipart/report
506       ``msg.get_content_maintype() == 'multipart'`` may return ``False``.  We
513          ...     print(part.get_content_maintype() == 'multipart',
523          multipart/report
552       When encountering a ``multipart/related``, check the ``start`` parameter
555       first (default root) part of the ``multipart/related``.
567       a ``multipart/related`` will return the object itself unless
579       of each of ``text/plain``, ``text/html``, ``multipart/related``, or
580       ``multipart/alternative`` (unless they are explicitly marked as
583       ``multipart/related``, return an iterator over the all the related parts
587       parts).  When applied directly to a ``multipart/alternative`` or a
588       non-``multipart``, return an empty iterator.
594       which will be empty for a non-``multipart``.  (See also
618       Convert a non-``multipart`` message into a ``multipart/related`` message,
620       (new) first part of the ``multipart``.  If *boundary* is specified, use
621       it as the boundary string in the multipart, otherwise leave the boundary
628       Convert a non-``multipart`` or a ``multipart/related`` into a
629       ``multipart/alternative``, moving any existing :mailheader:`Content-`
630       headers and payload into a (new) first part of the ``multipart``.  If
631       *boundary* is specified, use it as the boundary string in the multipart,
638       Convert a non-``multipart``, a ``multipart/related``, or a
639       ``multipart-alternative`` into a ``multipart/mixed``, moving any existing
641       ``multipart``.  If *boundary* is specified, use it as the boundary string
642       in the multipart, otherwise leave the boundary to be automatically
648       If the message is a ``multipart/related``, create a new message
650       and :meth:`~email.message.Message.attach` it to the ``multipart``.  If
651       the message is a non-``multipart``, call :meth:`make_related` and then
652       proceed as above.  If the message is any other type of ``multipart``,
661       If the message is a ``multipart/alternative``, create a new message
663       :meth:`~email.message.Message.attach` it to the ``multipart``.  If the
664       message is a non-``multipart`` or ``multipart/related``, call
666       any other type of ``multipart``, raise a :exc:`TypeError`. If
673       If the message is a ``multipart/mixed``, create a new message object,
675       :meth:`~email.message.Message.attach` it to the ``multipart``.  If the
676       message is a non-``multipart``, ``multipart/related``, or
677       ``multipart/alternative``, call :meth:`make_mixed` and then proceed as
704       following the headers, and the first multipart boundary string. Normally,