This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author leonardr
Recipients Pikamander2, berker.peksag, ezio.melotti, jkamdjou, kodial, leonardr, xtreak
Date 2020-06-12.20:56:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1591995364.72.0.866465626575.issue34480@roundup.psfhosted.org>
In-reply-to
Content
I'm the maintainer of Beautiful Soup. I learned about this issue when one of my users filed a bug for it against Beautiful Soup (https://bugs.launchpad.net/beautifulsoup/+bug/1883264).

BeautifulSoupHTMLParser (my subclass of html.parser.HTMLParser) implements error() only to prevent the NotImplementedError raised by ParserBase.error(). The docstring for my error() implementation says: "this method is called only on very strange markup and our best strategy is to pretend it didn't happen and keep going."

It shouldn't affect Beautiful Soup if, in a future version of Python, HTMLParser.error is never called and ParserBase is removed.
History
Date User Action Args
2020-06-12 20:56:04leonardrsetrecipients: + leonardr, ezio.melotti, berker.peksag, xtreak, kodial, jkamdjou, Pikamander2
2020-06-12 20:56:04leonardrsetmessageid: <1591995364.72.0.866465626575.issue34480@roundup.psfhosted.org>
2020-06-12 20:56:04leonardrlinkissue34480 messages
2020-06-12 20:56:04leonardrcreate