On 07/19/2008 07:14 PM, Davide Alberani wrote: > On Jul 18, "H. Turgut Uyar" <[EMAIL PROTECTED]> wrote: > > These changes make sense, and I'm convinced that we need a simple way > to express the "single" attribute (the result is a string), even if > I'm not sure _how_ to do it in a graceful way. :-) >
This will sound stupid, but I'm not sure what we want to mean by 'single'. Should it mean: a. I'm only interested in the first match (or any match). b. I'm sure that there will be only one match, so give it to me directly. If it is (b) we want, then practically the 'single' specification is unnecessary at the moment. Because there will be only one element in the resulting list and joining it using the empty string will produce the same result anyway. >> Extractor postprocessors are removed. > > Fine - probably we'll never need it. > I wanted to reduce the number of features that aim roughly the same thing: joiner, single, attribute postprocessor, and extractor postprocessor. My reasoning for removing the extractor postprocessor was that it did not provide a different context compared to the attribute postprocessor. It also had to be executed once for every attribute instead of once for every extractor. > After that, the usual run of: > ./test_parser.py -t -M 2>&1 | less > > will show the differences between old and new parsers. > That's great. Is there a shortcut for executing a specific test directly? Like movieParser.officialsites_parser or even movieParser.officialsites_parser_m17? Turgut ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
