Re: Error: no Python Codec for client encoding

From: Frank Kauff <fkauff(at)biologie(dot)uni-kl(dot)de>
To: psycopg(at)postgresql(dot)org
Subject: Re: Error: no Python Codec for client encoding
Date: 2011-10-20 11:55:07
Message-ID: 4EA00C1B.7090909@biologie.uni-kl.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

Hi Federico,

thanks for the change - but I'm not familiar with github, and have no
idea about cloning from the presoitory. The url won't work in Firefox.

Frank

On 10/20/2011 09:54 AM, Federico Di Gregorio wrote:
> On 20/10/11 09:45, Federico Di Gregorio wrote:
>> On 19/10/11 19:08, Daniele Varrazzo wrote:
>>> On Wed, Oct 19, 2011 at 5:59 PM, Frank Kauff<fkauff(at)biologie(dot)uni-kl(dot)de> wrote:
>>>>> Hi Daniele,
>>>>>
>>>>> it's a standard Zope installation and a psycopg installation out of the box
>>>>> - so I didn't change any configuration. How can i configure it so that is no
>>>>> longer an empty string?
>>> I have no idea, I'm not a zope user. Somebody else?
>> Don't know why Zope is passing an empty string. We should probably fix
>> the DA to use a sane default (UTF-8?)
> I just pushed to the devel branch a small change that, if Zope
> explicitly pass an empty "enc" argument just converts it to "utf-8".
> Frank, can you please clone from:
>
> git://luna.dndg.it/public/psycopg2 (devel branch)
>
> and test it?
>
> federico
>

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message Federico Di Gregorio 2011-10-20 11:55:46 Re: Error: no Python Codec for client encoding
Previous Message Federico Di Gregorio 2011-10-20 07:54:16 Re: Error: no Python Codec for client encoding