R. David Murray added the comment:
Andrea: yes, your patch is different from what I had in mind. The idea would
be to recognize the "nested part with duplicate boundary", register the new
defect, but produce a Message object with a structure that looked like this:
multipart/mixed
multipart/alternative
text/plain
text/html
image/gif
What your patch produces is:
multipart/mixed
multipart/alternative
text/plain
text/html
which is not recognizing the nested multipart or the final MIME part (which is
the OPs goal).
In principle it should be possible to parse the nesting despite the bad
boundary (other MIME parsers do it, as documented here), but I'm not sure how
hard it will be to modify Feedparser to do it. Looking at the code it seems
like it shouldn't be that hard to make it work, but I haven't dug deeply enough
to be sure.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27010>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
