Davide Alberani wrote: > Aaargh! My fault - there is no "imdbdom": at one time I just > introduced it to do some tests on my system, without messing > with the "normal" 'imdb' package. > I'll removed it from the CVS right now - just replacing > every "imdbdom" with "imdb". >
I'm still getting two errors. The first one is in http/__init__.py: from personParser import dom_person_main_parser There's no such definition in personParser.py. This import doesn't seem to be needed anyway, so I commented it out. The second problem is, when searching for a movie, the parser returns a list which the IMDbHTTPAccessSystem._searchMovie tries to index with the 'data' key as if it were a dictionary. > I can't think about any good name. :-) > "elements" is a bit too long; maybe "nodes"? Or is it misleading? > I think 'elements' is better than 'nodes', because, as I understand it, 'node' is a generic name that covers elements and attributes. > It's probabily a good idea (but not a top priority). > I'm more concerned about error handling: there are so many cases > where things can go bad, e.g.: feeding a movie page to the movie > search parser; it can happen if we have a direct match, but so > far the parser just _explodes_. ;-) > I noticed that when testing the company parser but I didn't attempt to solve it because I didn't know which class should be responsible for handling this. Turgut ------------------------------------------------------------------------- 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
