|
Size: 1696
Comment:
|
← Revision 12 as of 2010-03-08 17:11:56 ⇥
Size: 2412
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| Ideally, email 6.0 would be ready for Python 3.2 (release currently scheduled for 2010-06-26). In order to be ready for Python 3.2, we would need to be feature complete by the first scheduled beta (2010-04-03). 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, most likely sometime in the first half of 2012). 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. | Ideally, email 6.0 would be ready for Python 3.2 (release scheduled for 2010-12-11). In order to be ready for Python 3.2, we would need to be feature complete and field tested by the first scheduled beta (2010-09-18). If we can't be ready by then, we'll target Python 3.3 which will be 18-24 months after Python 3.2. In all cases, we'll provide standalone packages via the [[http://pypi.python.org/pypi|(cheeseshop)]] for older Python versions, including Python 2.x at least back to Python 2.6. |
| Line 13: | Line 13: |
| Note: the 3.2 release schedule is likely to be pushed out six months from the above dates. | R. David Murray applied for a grant from the PSF to work on implementing the proposed design. The PSF provided seed funding and offered support for further fundraising. (See Initiatives and Proposals below.) The initial work is ongoing, additional fundraising is not really in gear yet. |
| Line 19: | Line 19: |
| . [[http://www.bitdance.com/test/projects/email6/issues/|Open Issue Summary]] | |
| Line 24: | Line 25: |
| . [[/stdlibCLients|stdlib clients]] | |
| Line 25: | Line 27: |
| . [[http://www.bitdance.com/test/projects/email6/psfproposal/|PSF Grant Proposal]] . [[http://www.python.org/psf/records/board/minutes/2009-12-14/#funding-for-python-3-email-module|Notice of seed funding approval]] == Code == We've elected to host the code development in BZR on launchpad. . [[https://launchpad.net/python-email6|Launchpad Repository]] . [[http://www.bitdance.com/test/projects/email6/doc/email/|Docs snapshot]] |
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 scheduled for 2010-12-11). In order to be ready for Python 3.2, we would need to be feature complete and field tested by the first scheduled beta (2010-09-18). If we can't be ready by then, we'll target Python 3.3 which will be 18-24 months after Python 3.2. In all cases, we'll provide standalone packages via the (cheeseshop) for older Python versions, including Python 2.x at least back to Python 2.6.
R. David Murray applied for a grant from the PSF to work on implementing the proposed design. The PSF provided seed funding and offered support for further fundraising. (See Initiatives and Proposals below.) The initial work is ongoing, additional fundraising is not really in gear yet.
Resources
Initiatives and Proposals
Code
We've elected to host the code development in BZR on launchpad.