Fast question: is anyone still using the old http parsers (with IMDbPY
3.7 or CVS, that is)?
If yes, why?
My actual plan to drop the old parsers, already committed to the CVS:
- remove old "secondary" parsers as they are obsolete (e.g.: the old
"news" parser is broken, and so I've removed it).
- if oldParsers is set to True, BY DEFAULT you'll get an empty result,
trying to retrieve the related set of information (a warning is issued).
- if oldParsers is set to True and the new argument fallBackToNew is True
(default: False), a warning is issued and the _new_ corresponding parser
is used.
Once some of the main parsers (movies/plot/persons/bio/searches/...)
will be obsolete, I plan to remove the old parsers altogether.
On the programming side, everything needed to mark an old parser as
obsolete is:
- remove the old parser class ("HTMLSomethingParser").
- set the second item in the tuple of classes in the _OBJECTS dictionary
at the end of the file, to point to the new parser (so that, if both
points to the same class, we know that the old parser is gone).
--
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
