Message158195
| Author |
Jim.Jewett |
| Recipients |
Jim.Jewett, Michel.Leunen, ezio.melotti, georg.brandl, r.david.murray, serhiy.storchaka |
| Date |
2012年04月13日.02:55:34 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CA+OGgf6OpRsjCx5tUmgZTgpaUuKCytm6QpWVU9fAL8gX-VPG9g@mail.gmail.com> |
| In-reply-to |
<1334273197.95.0.798547085793.issue14538@psf.upfronthosting.co.za> |
| Content |
On Thu, Apr 12, 2012 at 7:26 PM, Ezio Melotti wrote:
> If HTMLParser doesn't parse as the HTML5 specs say,
> then it's considered a bug.
I had thought that was the goal of the html5lib, and that HTMLParser
was explicitly aiming at a much reduced model in order to remain
simple. (And also because the HTML5 spec is still changing fairly
often, particularly compared to the lifecycle of a feature release of
python.) |
|