In the CVS: - support for characters in 'sql'. - global configuration file for IMDbPY.
[characters in sql] Works a bit differently from the one in 'http' and 'mobile': we don't know which characters are _truly_ the same, amongst the list of played roles. All we have is the name of the character: every character with the same name is managed as it was just _one single_ character, portrayed in different movies. So we have a lot of "John" and "Jack" and even more of "Himself" and "Herself". In fact, sometimes there are so many of them that I've had to limit at 1000 the items in "filmography" returned for a given character (configurable with a parameter of the get_character method). The imdbpy2sql.py takes about 10/15% more time to complete, and uses 5/10% more space. At retrieve-time, the slow-down is not noticeable. I think this is a good solution, but... try it, and let me know what you think. [config file] I've introduced the "imdbpy.cfg" INI file, usable to configure the data access system globally (or the a single user). Now the default - if not specified in the code - is to search for this file and use it (if not found, 'http' is still used). I find it very useful; now you don't need to configure every IMDbPY-based program: a /etc/imdbpy.cfg or ~/.imdbpy.cfg file will be used by every program (it can still be override in the code). -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Imdbpy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
