Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings.

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Jan Urbański <wulczer(at)wulczer(dot)org>
Cc: hlinnaka(at)iki(dot)fi, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Asif Naeem <asif(dot)naeem(at)enterprisedb(dot)com>
Subject: Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings.
Date: 2012-07-05 21:30:52
Message-ID: 1341523852.16957.0.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On tor, 2012-07-05 at 22:53 +0200, Jan Urbański wrote:
> The problem is that PLyUnicode_Bytes is (via an ifdef) used as
> PyString_ToString on Python3, which means that there are numerous call
> sites and new ones might appear in any moment. I'm not that keen on
> invoking the traceback machinery on low-level encoding errors.

Why not?

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Jan Urbański 2012-07-05 21:54:26 Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings.
Previous Message Tom Lane 2012-07-05 21:17:03 pgsql: Don't try to trim "../" in join_path_components().

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2012-07-05 21:31:32 Re: Event Triggers reduced, v1
Previous Message Jan Urbański 2012-07-05 20:53:24 Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings.