On Jul 09, "H. Turgut Uyar" <[EMAIL PROTECTED]> wrote: > I doubt if it's realistic that parse_dom can handle such a complicated > data structure conversion and be generic at the same time.
Right, and maybe it's not worth the pain anyway. > > The problem is: how to express that? > > XSLT? :-) Woah! All I have kept, from my glorious XSLT days, are two books and nightmares! ;-) No, let's keep the parser as simple as possible. I've committed an implementation of DOMHTMLRatingsParser: there is a bit of code, but it's still less than half the old parser. In the next days I'll be painfully busy, after that I'll write some more parsers (they help to see if we're missing something). Another thing I want to do is to use the _ModuleProxy architecture to let old and new parsers selectable at runtime: it would be very useful for the transition phase. When you have time, the main thing to do is to write other parser, and see if parse_dom/extractors can be better defined/structured. PS: the new parser raise an exception, if used with bsoup. Thanks, -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
