Re: Time to drop plpython2?

From: Joe Conway <mail(at)joeconway(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Time to drop plpython2?
Date: 2022-02-18 21:08:33
Message-ID: 3684dcb4-4028-3c10-5dd9-37a503e7c670@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/18/22 15:53, Andres Freund wrote:
> the next run succeeded, with 'PYTHON' => 'python3' in build env. But
> presumably this just was because you installed the python3-devel package?

Ok, I guess I got confused when it failed due to the missing devel
package, because I removed the PYTHON => 'python3' from the build env
and it is still getting successfully past the configure stage. Sorry for
the noise.

Joe

--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2022-02-18 21:09:45 Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations
Previous Message Alvaro Herrera 2022-02-18 21:03:34 Re: Time to drop plpython2?