On 2008-02-20 11:15, Brett Cannon wrote:
On Feb 20, 2008 1:59 AM, Christian Heimes email@example.com wrote:
Brett Cannon wrote:
Here is an idea for an html package:
htmlentitydefs -> html.entities htmllib -> html.tools HTMLParser -> html.parser
What do people think?
What about markupbase and sgml?
markupbase has no public API and has already been renamed _markupbase.
As for sgmllib, since it only exists for htmllib, I say it should be merged into html.tools since there is no naming conflicts.
-1. SGML is a much more general markup language than HTML.
It's true that only htmllib does use sgmllib in the std lib, but there are applications out there that rely on sgmllib for the SGML part, e.g. ones implementing the DocBook tool chain.
But I just realized htmllib itself is a parser for html. So naming it html.tools seems wrong.
Perhaps it should be:
htmlentitydefs -> html.entities htmllib -> html.parser sgmllib -> html.parser HTMLParser -> html.xparser
That way the two different parsers are both delineated as parsers, but the fact that HTMLParser handles XHTML is covered.
I will also ask the web-sig if both parsers are really needed.
-Brett _______________________________________________ stdlib-sig mailing list firstname.lastname@example.org http://mail.python.org/mailman/listinfo/stdlib-sig