On Jul 16, "H. Turgut Uyar" <[EMAIL PROTECTED]> wrote: > As you predicted, parse_dom is becoming much more confusing. I'm > getting lost in it also, so I've started an attempt to simplify > it. I'll work from my home in the coming days, so I've committed > my changes for easier access; if you disagree with them, please > revert back :-)
I think these are exactly the kind of simplifications we need: the extractors must be as intuitive to write/read as possible. > My ideas are: Very good; I'm committing a small hack to handle empty strings (for test-suite and strange cases). I've also changed the DOMHTMLCharacterMaindetailsParser class: the deepcopy wasn't working correctly with Python 2.4 (it's still broken, but for other reasons: I think it's better to use postprocess_data(), to do the required magic). Right now I'm trying to use the old test-suite to compare the old parsers with the new ones. -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- 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
