On Fri, Jul 29, 2011 at 1:37 AM, Stefan Behnel <stefan...@behnel.de> wrote: > Brett Cannon, 28.07.2011 23:49: >> >> On Thu, Jul 28, 2011 at 11:25, Matt wrote: >>> >>> - What policies are in place for keeping parity with other HTML >>> parsers (such as those in web browsers)? >> >> There aren't any beyond "it would be nice". >> [...] >> It's more of an issue of someone caring enough to do the coding work to >> bring the parser up to spec for HTML5 (or introduce new code to live >> beside >> the HTML4 parsing code). > > Which, given that html5lib readily exists, would likely be a lot more work > than anyone who is interested in HTML5 handling would want to invest. > > I don't think we need a new HTML5 parsing implementation only to have it in > the stdlib. That's the old sunny Java way of doing it. >
I disaagree. Having proper html parsing out of the box is part of the "batteries included" thing. And it is not a matter of "having html 5" - as stated on this thread, fixing it for html5 will fix it for html that exists in the "real world". Python _has_ to work with quick 30-50 lines scripts deliverable everywhere, not just has proper 3rd party libraries that can work as part of a huge project using buildout. js -><- > Stefan > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/jsbueno%40python.org.br > _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
