Postgres Pro
Downloads
Home   >   mailing lists

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

From Daniele Varrazzo
Subject Re: Error: no Python Codec for client encoding
Date
Msg-id CA+mi_8bVLk3XwSzuVWuezgkpRkrsZOAjNA8zOxfNbEH9-FA=tw@mail.gmail.com
Whole thread Raw
In response to Error: no Python Codec for client encoding  (Frank Kauff <fkauff@biologie.uni-kl.de>)
Responses Re: Error: no Python Codec for client encoding  ("Frank Kauff" <fkauff@biologie.uni-kl.de>)
Re: Error: no Python Codec for client encoding  ("Frank Kauff" <fkauff@biologie.uni-kl.de>)
List psycopg
Tree view 
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

psycopg by date:

Previous
From: Mark Theisen
Date:
Subject: Re: connection already closed error
Next
From: "Frank Kauff"
Date:
Subject: Re: Error: no Python Codec for client encoding