Re: Proposal: Remove regress-python3-mangle.mk - Mailing list pgsql-hackers

From Yury Zhuravlev
Subject Re: Proposal: Remove regress-python3-mangle.mk
Date
Msg-id 27590f2a-9e23-415b-a833-3d2938a7b1ba@postgrespro.ru
Whole thread Raw
In response to Re: Proposal: Remove regress-python3-mangle.mk  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposal: Remove regress-python3-mangle.mk
List pgsql-hackers
Tom Lane wrote:
> Also, I would bet that those tools would not know anything
> about converting PL language names between 'plpythonu' and 'plpython2u'
> and 'plpython3u'; so even if we used one of them, we would still need a
> layer pretty similar to what we have.

I do not see this as a problem because we can build Postgres only with one
version of Python (2 or 3).
Or am I missing something?

>may be a bit of a kluge
For python developer it is really strange...


PS I see Postgres philosophy - do not touch what works well, even if it
looks terrible. :)
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: max_parallel_degree > 0 for 9.6 beta
Next
From: Tom Lane
Date:
Subject: Should XLogInsert() be done only inside a critical section?