Peter Eisentraut <peter_e@gmx.net> writes:
> On 3/11/16 1:16 PM, Tom Lane wrote:
>> Doesn't matter. We support both Python 2 and 3, and this script must
>> do so as well, else it's not getting committed.
> This script is only run occasionally when the unaccent data needs to be
> updated from Unicode data, so it's not really that important what
> language and version it's written in.
Oh, okay, I'd supposed this would be part of the build process.
> That said, the mentioned reason
> for changing this to Python 3 is so that one can include Unicode
> characters into the source text, which I find undesirable in general
> (for PostgreSQL source code) and not very useful in this particular
> case. I think the script can be kept in Python 2 style.
Works for me, and I agree that Unicode in our source text is mostly
a pain.
regards, tom lane
