Re: BUG #13440: unaccent does not remove all diacritics

From: Léonard Benedetti <benedetti(at)mlpo(dot)fr>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13440: unaccent does not remove all diacritics
Date: 2016-03-11 17:14:58
Message-ID: 56E2FD12.2000102@mlpo.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

11/03/2016 17:38, Teodor Sigaev wrote:
>> Here is the patch, attached.
>
> Hmm, now script doesn't work with Python 2:
> % python2 -V
> Python 2.7.11
> % python2 contrib/unaccent/generate_unaccent_rules.py
> File "contrib/unaccent/generate_unaccent_rules.py", line 7
> SyntaxError: Non-ASCII character '\xe2' in file
> contrib/unaccent/generate_unaccent_rules.py on line 7, but no encoding
> declared; see http://python.org/dev/peps/pep-0263/ for details
>
> Is it intentional?
>
In fact, Python 3 is not backward-compatible. This version brings many
new features which are not compatible with Python 2, so it is
intentional. To quote the documentation: “Python 3.0 […] is the first
ever intentionally backwards incompatible Python release”.

Despite all that, I think this transition to Python 3 is wise, it is
available since 2008. Python 2 is legacy and its last version (2.7) is a
“end-of-life release”.

Léonard Benedetti

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-03-11 18:16:05 Re: BUG #13440: unaccent does not remove all diacritics
Previous Message David G. Johnston 2016-03-11 17:02:01 Re: BUG #14016: Incomplete documentation of IN subquery expression