[issue8885] markupbase declaration errors aren't recoverable

Changes by Ezio Melotti : -- resolution: -> out of date stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue8885] markupbase declaration errors aren't recoverable

Ezio Melotti added the comment: Because even on 2.7 the parser is now able to handle broken markup, so "error" won't be called anymore. -- ___ Python tracker ___ ___

[issue8885] markupbase declaration errors aren't recoverable

Mark Nottingham added the comment: Why remove 2.7? It'd be an easy bug fix if j is incremented. -- ___ Python tracker ___ ___ Python-b

[issue8885] markupbase declaration errors aren't recoverable

Ezio Melotti added the comment: s/non-strict/strict/ -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue8885] markupbase declaration errors aren't recoverable

Ezio Melotti added the comment: HTMLParser shouldn't raise errors anymore, so the "error" method (and probably the HTMLParseError exception too) should be deprecated along with the non-strict mode on 3.3. -- assignee: -> ezio.melotti nosy: +ezio.melotti type: behavior -> enhancement

[issue8885] markupbase declaration errors aren't recoverable

Terry J. Reedy added the comment: I verified the looping behavior of the testcase in both 2.7.1 and, with minor mods, 3.1.3 and 3.2b1, so this is a valid issue. The HTMLParcer docs (2.7, 3.2) do not mention the .error method. The default is def error(self, message): raise HTMLParse

[issue8885] markupbase declaration errors aren't recoverable

Changes by Éric Araujo : -- nosy: +eric.araujo resolution: invalid -> stage: -> needs patch title: markerbase declaration errors aren't recoverable -> markupbase declaration errors aren't recoverable versions: +Python 2.7 -Python 2.6 ___ Python tra