And an improvement:
- better SQL statements for the creation of temporary tables (re)storing
imdbIDs... it should work gracefully with postgresql and possibly
other databases.
As usual, please report any problem and strange behavior: I'm not too sure
about the consequences of these changes. :-)
--
Davide Alberani <davide....@gmail.com> [PGP KeyID: 0x465BFD47]
http://www.mimante.net/
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Imdbpy-devel mailing list
Imdbpy...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
Hi and pardo for the delay: very busy weeks.
> Both features seem very interesting, will reraiseExceptions allow us to
> catch Exceptions from our own programs?
Yes, that's the idea. Not much tested, as usual. :-P
> I haven't figured out a way to properly intercept an Exception (for example,
> a connection error) raised by the imdbpy module from my own code to, allow
> the operation to be retried, for example. I assume that setting
> reraiseExceptions and catching them from my own code should work, right?
The IMDbPY exceptions are organized in a small hierarchy:
- IMDbError : Base class for every exception raised by the imdb package.
|
+-> IMDbDataAccessError: unable to access some data
+-> IMDbParserError : unable to parse something
You can import them from the imdb._exceptions module.
If you want to catch them all, use IMDbError.