Python 2.4 final will probably be released in a few hours so this seems
like a good time to release the standalone email package, version 3.0
final. Unless there's some last second snafu, this will be identical to
the version released with Python 2.4.
email 3.0 is compatible with Python 2.3 and 2.4. If you need to support
earlier versions of Python, stick with email 2.5.5. For documentation
(until Fred flips the "current" docs switch) and download links, please
see the email-sig home page:
Changes in email 3.0 include:
* New FeedParser provides an incremental parsing API for
applications that may need to read email messages from blocking
sources (e.g. sockets). FeedParser is also more standards
compliant than the old parser and is "non-strict", so that it
should never raise parse errors when parsing broken messages.
* The old Parser API is (mostly) supported for backward
compatibility.
* Previously deprecated API features have been removed, while a
few more deprecations have been added.
* Support for Pythons earlier than 2.3 have been removed.
* Lots and lots of fixes.
Feel free to join the email-sig mailing list for further discussion.
-Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iQCVAwUAQarMv3E jvBPtnXfVAQI4kQ QAgr6mcGgfVx+vh AhAPSH4OkqxUzbU 8Sye
uNa9owLqULrmbZM qUi+Gpasea1rhfF 8Y8DPDnI+J098ua QhGqWMGbDzMYTXw EfBP
QP5daiEXabLOBjC 7Uy/Clb/ZT0F/Ld+oz6ImlymHvki EGp31w49C1nEu1t G3eAM1
NppFw7mCifU=
=Lzeq
-----END PGP SIGNATURE-----
like a good time to release the standalone email package, version 3.0
final. Unless there's some last second snafu, this will be identical to
the version released with Python 2.4.
email 3.0 is compatible with Python 2.3 and 2.4. If you need to support
earlier versions of Python, stick with email 2.5.5. For documentation
(until Fred flips the "current" docs switch) and download links, please
see the email-sig home page:
Changes in email 3.0 include:
* New FeedParser provides an incremental parsing API for
applications that may need to read email messages from blocking
sources (e.g. sockets). FeedParser is also more standards
compliant than the old parser and is "non-strict", so that it
should never raise parse errors when parsing broken messages.
* The old Parser API is (mostly) supported for backward
compatibility.
* Previously deprecated API features have been removed, while a
few more deprecations have been added.
* Support for Pythons earlier than 2.3 have been removed.
* Lots and lots of fixes.
Feel free to join the email-sig mailing list for further discussion.
-Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iQCVAwUAQarMv3E jvBPtnXfVAQI4kQ QAgr6mcGgfVx+vh AhAPSH4OkqxUzbU 8Sye
uNa9owLqULrmbZM qUi+Gpasea1rhfF 8Y8DPDnI+J098ua QhGqWMGbDzMYTXw EfBP
QP5daiEXabLOBjC 7Uy/Clb/ZT0F/Ld+oz6ImlymHvki EGp31w49C1nEu1t G3eAM1
NppFw7mCifU=
=Lzeq
-----END PGP SIGNATURE-----