On May 11, Sabo <[EMAIL PROTECTED]> wrote:
> It worked fine (106 minutes with 2 dual core opterons and 4GB
> of ram).
Was this computer busy doing other CPU-intensive duties?
On a monster like that, I was hoping for better performances. :-)
> imdbpy2sql.py:727: Warning: Data truncated for column
It worked fine (106 minutes with 2 dual core opterons and 4GB of ram). Only
thing I noticed is a lot of these messages popping up while it was running.
I'm not sure they were happening before.
SCANNING actor: Hammer, M.C.
SCANNING actor: Hannon, Chick
* FLUSHING PersonsCache...
imdbpy2sql.py:727:
On May 10, Sabo <[EMAIL PROTECTED]> wrote:
> Thanks. The original CVS version gave this:
[...]
> TypeError: build_title() got an unexpected keyword argument '_emptyString'
Wait: it seems that you're using the imdbpy2sql.py script from the
CVS, but you've not installed the imdbpy package from th
Thanks. The original CVS version gave this:
SCANNING movies: Waiting (2006/I) (movieID: 470001)
SCANNING movies: Will of the Wisp (2007) (movieID: 480001)
SCANNING movies: Yuvana dön baba (1968) (movieID: 490001)
* FLUSHING MoviesCache...
Traceback (most recent call last):
File "imdbpy2sql.py",
On May 09, Jon Sabo <[EMAIL PROTECTED]> wrote:
> As I'm not at the machine now I'm not sure what version of mysql I'm
> running. I don't imagine that's the problem, but I'm not entirely
> certain how to fix it (my knowledge of unicode is quite poor).
Heee... you're not alone... ;-)
Unicode is f
5 matches
Mail list logo
