[issue6662] HTMLParser.HTMLParser doesn't handle malformed charrefs

2010-05-24 Thread STINNER Victor
STINNER Victor added the comment: Commited: 2.7 (r81500, r81501), 2.6 (r81503), 3.2 (r81504), 3.1 (r81505). -- nosy: +haypo resolution: -> fixed status: open -> closed ___ Python tracker __

[issue6662] HTMLParser.HTMLParser doesn't handle malformed charrefs

2010-05-24 Thread Éric Araujo
Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue6662] HTMLParser.HTMLParser doesn't handle malformed charrefs

2010-04-28 Thread Fredrik Håård
Fredrik Håård added the comment: Confirmed on trunk. Attached a (what I think is) minimal patch to fix, together with a tweak of existing unit test case to verify it. -- keywords: +patch versions: +Python 2.7 Added file: http://bugs.python.org/file17117/Issue6662.patch ___

[issue6662] HTMLParser.HTMLParser doesn't handle malformed charrefs

2010-04-27 Thread Fredrik Håård
Fredrik Håård added the comment: Is there a reason for HTMLParser to treat anything that does not match the regex '&#\d+;' as a charref? -- ___ Python tracker ___ _

[issue6662] HTMLParser.HTMLParser doesn't handle malformed charrefs

2010-04-27 Thread Fredrik Håård
Changes by Fredrik Håård : -- nosy: +fredrik.haard ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue6662] HTMLParser.HTMLParser doesn't handle malformed charrefs

2009-08-25 Thread Ezio Melotti
Ezio Melotti added the comment: Confirmed on Python3.1 too. -- nosy: +ezio.melotti priority: -> high ___ Python tracker ___ ___ Pytho

[issue6662] HTMLParser.HTMLParser doesn't handle malformed charrefs

2009-08-06 Thread Dave Day
New submission from Dave Day : When HTMLParser.HTMLParser encounters a malformed charref (for example &#bad;) it no longer parsers the following HTML correctly. For example: &#bad; Recognises the starttag "p" but considers the rest to be data. To reproduce: class MyParser(HTMLParser.HTMLPars