Still no luck :/ maybe the problem is in some environmental variables or
settings, which on installed version are present, but running from source
are missing or incorrect?
What about this, i printed out some variables:
print sys.stdout.encoding -> UTF-8
print sys.stdin.encoding -> UTF-8
print sys.getdefaultencoding(); -> ascii
Is it ok that sys.getdefaultencoding(); == ascii ?
Maybe there are some more variables i should check?
On Tue, Apr 19, 2011 at 11:11 PM, Davide Alberani <davide.alber...@gmail.com
> wrote:
> On Mon, Apr 18, 2011 at 09:30, Davide Alberani
> <davide.alber...@gmail.com> wrote:
> >
> > Thanks for the file, I hope to look at it within a day or two.
>
> Ok: the file is correctly encoded in iso8859-1, as expected, and contains
> no garbage.
>
> Using it as the only input for imdbpy2sql.py (putting the attached file in
> a directory by itself), I can run the script with no errors (besides
> the expected
> warnings about missing files).
>
> I'm using the version from the Mercurial repository, without the cutils.so
> library.
>
> Please, if you can't install IMDbPY in your system, consider the use
> of virtualenv.
> Having tried that, I have to recommend you to double check the
> settings of your Postgresql server for some kind of incoherences
> about encodings and collations.
>
> HTH,
> --
> Davide Alberani <davide.alber...@gmail.com> [PGP KeyID: 0x465BFD47]
> http://www.mimante.net/
>
------------------------------------------------------------------------------
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
