| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hugh Ranalli <hugh(at)whtc(dot)ca>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, thomas(dot)munro(at)enterprisedb(dot)com, Daniel Verite <daniel(at)manitou-mail(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15548: Unaccent does not remove combining diacritical characters |
| Date: | 2019-01-03 01:15:22 |
| Message-ID: | 20190103011522.GA2107@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Jan 02, 2019 at 02:32:32PM -0500, Tom Lane wrote:
> Seeing that supporting python 2 only adds a dozen lines of code,
> I vote for retaining it for now. It'd be appropriate to drop that when
> python 3 is the overwhelmingly more-installed version, but AFAICT that
> isn't the case yet.
As a side note, if I recall correctly Python 2.7 will be EOL'd in
2020 by community, though I suspect that a couple of vendors will
still maintain compatibility for a couple of years in what they ship.
CentOS and RHEL enter in this category perhaps. Like Peter, I would
vote for just maintaining support for Python 3 in this script, as any
modern development machines have it anyway, and not a lot of commits
involve it (I am counting 4 since 2015).
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | lichuancheng@highgo.com | 2019-01-03 09:50:48 | BUG #15567: Wal receiver process restart failed when a damaged wal record arrived at standby. |
| Previous Message | Alvaro Herrera | 2019-01-02 22:54:03 | Re: Is temporary functions feature official/supported? Found some issues with it. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2019-01-03 03:58:12 | Re: Logical decoding for operations on zheap tables |
| Previous Message | Michael Paquier | 2019-01-03 01:03:53 | Re: [PATCH] check for ctags utility in make_ctags |