Re: Error: no Python Codec for client encoding - Mailing list psycopg

From Frank Kauff
Subject Re: Error: no Python Codec for client encoding
Date
Msg-id web-87385945@uni-kl.de
Whole thread Raw
In response to Re: Error: no Python Codec for client encoding  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
Responses Re: Error: no Python Codec for client encoding  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
List psycopg
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?

Frank



On Wed, 19 Oct 2011 17:27:12 +0100
  Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote:
> On Wed, Oct 19, 2011 at 4:41 PM, Frank Kauff
><fkauff@biologie.uni-kl.de> wrote:
>
>>>    Module Products.ZPsycopgDA.db, line 50, in getconn
>
> This line only does
>
>    conn.set_client_encoding(self.encoding)
>
> and self.encoding is passed to the DB constructor. It is
>configured to
> be an empty string, which we don't like. Where does this
>empty string
> come from? I suspect misconfiguration.
>
> -- Daniele
>
> --
> Sent via psycopg mailing list (psycopg@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/psycopg

--

psycopg by date:

Previous
From: Daniele Varrazzo
Date:
Subject: Re: Error: no Python Codec for client encoding
Next
From: Daniele Varrazzo
Date:
Subject: Re: Error: no Python Codec for client encoding