Differences between revisions 1 and 2
Revision 1 as of 2009-04-02 18:33:47
Size: 1384
Editor: BarryWarsaw
Comment:
Revision 2 as of 2009-10-08 22:03:48
Size: 1366
Editor: RDavidMurray
Comment: update target release and dates
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The [[http://www.python.org/doc/current/library/email.html|email package]] is a large, complicated package that comes with Python, and which supports parsing, manipulating and generating email messages in RFC compliant formats. Its development is ongoing. Current focus is on version 6.0, with a target release in Python 3.1 (back ported to Python 2.7), and with standalone packages available to older versions of Python. The [[http://www.python.org/doc/current/library/email.html|email package]] is a large, complicated package that comes with Python, and which supports parsing, manipulating and generating email messages in RFC compliant formats. Its development is ongoing. Current focus is on version 6.0, with a target release in Python 3.2 (back ported to Python 2.7), and with standalone packages available to older versions of Python.
Line 11: Line 11:
Ideally, email 6.0 would be ready for Python 3.1 [[http://www.python.org/dev/peps/pep-0375/|(release schedule)]]. In order to be ready for Python 3.1, we would need to be feature complete by the first scheduled beta on May 2, 2009. If we can't be ready by then, we'll target Python 3.2 which will likely be 18-24 months after Python 3.1 (so, something like beginning of 2011). In all cases, we'll provide standalone packages via the [[http://pypi.python.org/pypi|(cheeseshop)]] for all older versions, include Python 2.x at least back to Python 2.5. Ideally, email 6.0 would be ready for Python 3.2 (release tentatively scheduled for summer or early fall of 2010). In order to be ready for Python 3.2, we would need to be feature complete by the first scheduled beta. If we can't be ready by then, we'll target Python 3.3 which will likely be 18-24 months after Python 3.2 (so, something like start of 2013). In all cases, we'll provide standalone packages via the [[http://pypi.python.org/pypi|(cheeseshop)]] for all older versions, include Python 2.x at least back to Python 2.6.

The email package SIG

The email package is a large, complicated package that comes with Python, and which supports parsing, manipulating and generating email messages in RFC compliant formats. Its development is ongoing. Current focus is on version 6.0, with a target release in Python 3.2 (back ported to Python 2.7), and with standalone packages available to older versions of Python.

The information and pages below are used to record decisions and status related to the email package's development. Discussions should be conducted on the Email SIG mailing list (archive).

Goals

Schedule and Status

Ideally, email 6.0 would be ready for Python 3.2 (release tentatively scheduled for summer or early fall of 2010). In order to be ready for Python 3.2, we would need to be feature complete by the first scheduled beta. If we can't be ready by then, we'll target Python 3.3 which will likely be 18-24 months after Python 3.2 (so, something like start of 2013). In all cases, we'll provide standalone packages via the (cheeseshop) for all older versions, include Python 2.x at least back to Python 2.6.

Initiatives and Proposals

Email SIG (last edited 2010-03-08 17:11:56 by c-24-91-29-50)

Unable to edit the page? See the FrontPage for instructions.