summaryrefslogtreecommitdiffstats
path: root/Doc/using
diff options
context:
space:
mode:
authorR David Murray <rdmurray@bitdance.com>2012-06-24 09:03:27 (GMT)
committerR David Murray <rdmurray@bitdance.com>2012-06-24 09:03:27 (GMT)
commit97f43c019f3bb8376a3a5f7bc52e97b4c2ed8e16 (patch)
tree276e118773eb8b022e7674a14d8e2af8d38f70a6 /Doc/using
parent49c15d4a5fa139bf2d154112709a8b29c9d5d678 (diff)
downloadcpython-97f43c019f3bb8376a3a5f7bc52e97b4c2ed8e16.zip
cpython-97f43c019f3bb8376a3a5f7bc52e97b4c2ed8e16.tar.gz
cpython-97f43c019f3bb8376a3a5f7bc52e97b4c2ed8e16.tar.bz2
#15160: Extend the new email parser to handle MIME headers.
This code passes all the same tests that the existing RFC mime header parser passes, plus a bunch of additional ones. There are a couple of commented out tests where there are issues with the folding. The folding doesn't normally get invoked for headers parsed from source, and the cases are marginal anyway (headers with invalid binary data) so I'm not worried about them, but will fix them after the beta. There are things that can be done to make this API even more convenient, but I think this is a solid foundation worth having. And the parser is a full RFC parser, so it handles cases that the current parser doesn't. (There are also probably cases where it fails when the current parser doesn't, but I haven't found them yet ;) Oh, yeah, and there are some really ugly bits in the parser for handling some 'postel' cases that are unfortunately common. I hope/plan to to eventually refactor a lot of the code in the parser which should reduce the line count...but there is no escaping the fact that the error recovery is welter of special cases.
Diffstat (limited to 'Doc/using')
0 files changed, 0 insertions, 0 deletions