traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
cpython/Lib/email/MIMEText.py

29 lines
981 B
Python
Raw Normal View History

Big email 3.0 API changes, with updated unit tests and documentation. Briefly (from the NEWS file): - Updates for the email package: + All deprecated APIs that in email 2.x issued warnings have been removed: _encoder argument to the MIMEText constructor, Message.add_payload(), Utils.dump_address_pair(), Utils.decode(), Utils.encode() + New deprecations: Generator.__call__(), Message.get_type(), Message.get_main_type(), Message.get_subtype(), the 'strict' argument to the Parser constructor. These will be removed in email 3.1. + Support for Python earlier than 2.3 has been removed (see PEP 291). + All defect classes have been renamed to end in 'Defect'. + Some FeedParser fixes; also a MultipartInvariantViolationDefect will be added to messages that claim to be multipart but really aren't. + Updates to documentation.
2004-10-03 00:16:19 -03:00
# Copyright (C) 2001-2004 Python Software Foundation
# Author: Barry Warsaw
# Contact: email-sig@python.org
The email package version 1.0, prototyped as mimelib <http://sf.net/projects/mimelib>. There /are/ API differences between mimelib and email, but most of the implementations are shared (except where cool Py2.2 stuff like generators are used).
2001-09-23 00:17:28 -03:00
Big email 3.0 API changes, with updated unit tests and documentation. Briefly (from the NEWS file): - Updates for the email package: + All deprecated APIs that in email 2.x issued warnings have been removed: _encoder argument to the MIMEText constructor, Message.add_payload(), Utils.dump_address_pair(), Utils.decode(), Utils.encode() + New deprecations: Generator.__call__(), Message.get_type(), Message.get_main_type(), Message.get_subtype(), the 'strict' argument to the Parser constructor. These will be removed in email 3.1. + Support for Python earlier than 2.3 has been removed (see PEP 291). + All defect classes have been renamed to end in 'Defect'. + Some FeedParser fixes; also a MultipartInvariantViolationDefect will be added to messages that claim to be multipart but really aren't. + Updates to documentation.
2004-10-03 00:16:19 -03:00
"""Class representing text/* type MIME documents."""
The email package version 1.0, prototyped as mimelib <http://sf.net/projects/mimelib>. There /are/ API differences between mimelib and email, but most of the implementations are shared (except where cool Py2.2 stuff like generators are used).
2001-09-23 00:17:28 -03:00
Use absolute import paths for intrapackage imports. Use MIMENonMultipart as the base class so that you can't attach() to these non-multipart message types.
2002-06-02 16:05:08 -03:00
from email.MIMENonMultipart import MIMENonMultipart
from email.Encoders import encode_7or8bit
The email package version 1.0, prototyped as mimelib <http://sf.net/projects/mimelib>. There /are/ API differences between mimelib and email, but most of the implementations are shared (except where cool Py2.2 stuff like generators are used).
2001-09-23 00:17:28 -03:00
Give me back my page breaks.
2001-10-04 14:05:11 -03:00
Use absolute import paths for intrapackage imports. Use MIMENonMultipart as the base class so that you can't attach() to these non-multipart message types.
2002-06-02 16:05:08 -03:00
class MIMEText(MIMENonMultipart):
The email package version 1.0, prototyped as mimelib <http://sf.net/projects/mimelib>. There /are/ API differences between mimelib and email, but most of the implementations are shared (except where cool Py2.2 stuff like generators are used).
2001-09-23 00:17:28 -03:00
"""Class for generating text/* type MIME documents."""
Big email 3.0 API changes, with updated unit tests and documentation. Briefly (from the NEWS file): - Updates for the email package: + All deprecated APIs that in email 2.x issued warnings have been removed: _encoder argument to the MIMEText constructor, Message.add_payload(), Utils.dump_address_pair(), Utils.decode(), Utils.encode() + New deprecations: Generator.__call__(), Message.get_type(), Message.get_main_type(), Message.get_subtype(), the 'strict' argument to the Parser constructor. These will be removed in email 3.1. + Support for Python earlier than 2.3 has been removed (see PEP 291). + All defect classes have been renamed to end in 'Defect'. + Some FeedParser fixes; also a MultipartInvariantViolationDefect will be added to messages that claim to be multipart but really aren't. + Updates to documentation.
2004-10-03 00:16:19 -03:00
def __init__(self, _text, _subtype='plain', _charset='us-ascii'):
The email package version 1.0, prototyped as mimelib <http://sf.net/projects/mimelib>. There /are/ API differences between mimelib and email, but most of the implementations are shared (except where cool Py2.2 stuff like generators are used).
2001-09-23 00:17:28 -03:00
"""Create a text/* type MIME document.
__init__(): Don't add a newline to _text if it doesn't already end in one. Possibly controversial.
2003-03-11 01:04:09 -04:00
_text is the string for this message object.
The email package version 1.0, prototyped as mimelib <http://sf.net/projects/mimelib>. There /are/ API differences between mimelib and email, but most of the implementations are shared (except where cool Py2.2 stuff like generators are used).
2001-09-23 00:17:28 -03:00
Image.py and class Image => MIMEImage.py and MIMEImage Text.py and class Text => MIMEText.py and MIMEText MessageRFC822.py and class MessageRFC822 => MIMEMessage.py and MIMEMessage These are renamed so as to be more consistent; these are MIME specific derived classes for when creating the object model out of whole cloth.
2001-09-26 02:34:30 -03:00
_subtype is the MIME sub content type, defaulting to "plain".
The email package version 1.0, prototyped as mimelib <http://sf.net/projects/mimelib>. There /are/ API differences between mimelib and email, but most of the implementations are shared (except where cool Py2.2 stuff like generators are used).
2001-09-23 00:17:28 -03:00
Docstring consistency with the updated .tex files.
2002-09-30 21:52:27 -03:00
_charset is the character set parameter added to the Content-Type
Sync'ing with standalone email package 2.0.1. This adds support for non-us-ascii character sets in headers and bodies. Some API changes (with DeprecationWarnings for the old APIs). Better RFC-compliant implementations of base64 and quoted-printable. Updated test cases. Documentation updates to follow (after I finish writing them ;).
2002-04-10 18:01:31 -03:00
header. This defaults to "us-ascii". Note that as a side-effect, the
Docstring consistency with the updated .tex files.
2002-09-30 21:52:27 -03:00
Content-Transfer-Encoding header will also be set.
The email package version 1.0, prototyped as mimelib <http://sf.net/projects/mimelib>. There /are/ API differences between mimelib and email, but most of the implementations are shared (except where cool Py2.2 stuff like generators are used).
2001-09-23 00:17:28 -03:00
"""
Use absolute import paths for intrapackage imports. Use MIMENonMultipart as the base class so that you can't attach() to these non-multipart message types.
2002-06-02 16:05:08 -03:00
MIMENonMultipart.__init__(self, 'text', _subtype,
**{'charset': _charset})
Sync'ing with standalone email package 2.0.1. This adds support for non-us-ascii character sets in headers and bodies. Some API changes (with DeprecationWarnings for the old APIs). Better RFC-compliant implementations of base64 and quoted-printable. Updated test cases. Documentation updates to follow (after I finish writing them ;).
2002-04-10 18:01:31 -03:00
self.set_payload(_text, _charset)