> I'm sure that some (many?) complex parser will require some (a lot > of?) code to be written, but there are also many simpler code. > Do you think these can be handled by a generic "feed_dom" code, > using a set of provided parameters (like the one you've put in > the _k dictionary of the HTMLSearchMovieParser class)? >
I've tried to implement a more generic dom parser (parse_dom in the ParserBase class). It will use the rules as defined by the _paths attribute in the current parser. I've adapted the search parsers to this method and also written part of the person main details parser. I hope it holds up for other parsers as well. Turgut > By the way: I think it's time to give up to the _ModuleProxy approach: > let's leave it in place to be used by ParserBase-based parsers, but > it was just a bad idea. > > Actually I'm studing the bases of XPath: once a stable design is in > place, I hope I'll be ready to start writing some parsers. > > > Thanks! > > +++ > [1] so far I won't touch the IMDbURLopener, even if it's guessing > for encodings can be handled better by BeautifoulSoup and friends. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
