Re: Error: no Python Codec for client encoding

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Frank Kauff <fkauff(at)biologie(dot)uni-kl(dot)de>
Cc: psycopg(at)postgresql(dot)org
Subject: Re: Error: no Python Codec for client encoding
Date: 2011-10-19 16:27:12
Message-ID: CA+mi_8bVLk3XwSzuVWuezgkpRkrsZOAjNA8zOxfNbEH9-FA=tw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

On Wed, Oct 19, 2011 at 4:41 PM, Frank Kauff <fkauff(at)biologie(dot)uni-kl(dot)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

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message Frank Kauff 2011-10-19 16:59:42 Re: Error: no Python Codec for client encoding
Previous Message Mark Theisen 2011-10-19 15:45:59 Re: connection already closed error