On Sun, Apr 17, 2011 at 5:13 PM, Davide Alberani <davide.alber...@gmail.com>wrote:
> On Sun, Apr 17, 2011 at 14:04, darklow <dark...@gmail.com> wrote: > > Updated this morning to latest data files, no change and unfortunately > this > > fix also doesn't work. > > Hmm... to debug a problem like this without being able to reproduce, > is extremely difficult. :-/ > > > This error started when we uninstalled imdbpy (left all the dependency > libs) > > and started run it without installation. Maybe there is some kind of > problem > > and some kind of hidden unicode dependencies? Maybe you can try to run > > without installation, jus from source? > > Have you some very good reason to do so? :-) > We have Debian linux on our server and our sysadmin allows only stable packs. However latest version of imdbpy has these md5 checksum that are quite important in our situation, that is why i have to run it from source. > Can't you try to purge every reference to IMDbPY left on the > system (search for the scripts in /usr/bin/ and /usr/local/bin/ and > be sure that "import imdb" fails, at the python prompt) and see > if the problem is solved, after IMDbPY 4.7 is reinstalled? > > Unfortunately right now i can't do reinstall, just to run it by source. However if this is the reason and there will be no way to fix this, i'll try to convince sysadmin to install this version from unofficial debian packs > If you have problems locating the IMDbPY package, just open > the Python prompt and: > >>> import imdb > >>> print imdb > > > Also every time i start the script i receive two warnings: > > 2011-04-17 11:13:37,398 WARNING [imdbpy.parser.sql.aux] > > /data/web/imdb/imdbpy4.7-159671/imdb/parser/sql/__init__.py:125: Unable > to > > import the cutils.ratcliff function. Searching names and titles using > the > > "sql" data access system will be slower. > > This will force IMDbPY to use some pure-python fall-back functions. > It's entirely possible that there are some bug in these functions, even > if a run without cutils.so is running fine, for me (so far). > > > IMPORTING psyco... FAILED (not a big deal, everything is alright...) > > That's not a problem for sure. > > Right now, my first guess is that somewhere, after the *.list files ar > read and turned into utf-8 encoded strings, the imdbpy2sql.py > script does Something Very Wrong(tm) to a string (like cutting it at a > certain > place, ending up cutting a single utf-8 encoded char in two: this could > explain the error). > > I've tried the conversion suggested by Petite Abeille, and it works fine. > > Please, could you cut a small piece (few kilobytes) of the actors.list > file, > and attach it (no cut-and-paste)? > It goes without saying that you should chose a portion where you see > (or guess are) the "strange chars" :-) > I attached the small part of actors.list file right the place with the broken characters (used unix sed command to cut the problematic lines out). > > Thanks! > > -- > Davide Alberani <davide.alber...@gmail.com> [PGP KeyID: 0x465BFD47] > http://www.mimante.net/ >
actors.list.small
Description: Binary data
------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________ Imdbpy-help mailing list Imdbpy-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-help
