| From: | Patrik Novotny <panovotn(at)redhat(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL Packagers <pgsql-packagers(at)postgresql(dot)org>, git(at)rmr(dot)ninja |
| Subject: | Re: plpythonu -> python3 |
| Date: | 2019-11-07 17:56:34 |
| Message-ID: | CAE_EZkghvUt7W_D+hJyDAm2LMfHY=K8GtxYKwJw8nYw1yaUfBw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 7, 2019 at 6:04 PM Christoph Berg <myon(at)debian(dot)org> wrote:
> How do other packagers handle that? Are you still supporting python2?
> Would it be ok to make plpythonu.control point at python3 in PG12 in
> Debian, even the upstream default is still python2?
Speaking for Fedora and RHEL, I'd say the best way to approach this from the
packager standpoint would be to simply stop building plpython2 for releases
without python2 support.
> Would it be ok to make plpythonu.control point at python3 in PG12 in
> Debian, even the upstream default is still python2?
IMHO, this should be done upstream. The reason for this would be to have
a uniform approach to this across distributions, and it is explained
in more detail
in some of the older threads of this list.
--
Patrik Novotný
Associate Software Engineer
Red Hat
panovotn(at)redhat(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-11-07 17:57:38 | Re: plpythonu -> python3 |
| Previous Message | Christoph Berg | 2019-11-07 17:38:53 | Re: plpythonu -> python3 |