Removing the PL/Py entry sounds right to me. How about adding plv8 (https://github.com/plv8/plv8) at the same time?
On Fri, Dec 7, 2018 at 9:16 AM Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > On 2018-Dec-07, Alvaro Herrera wrote: > > > On 2018-Dec-07, PG Doc comments form wrote: > > > > > The following documentation comment has been logged on the website: > > > > > > Page: https://www.postgresql.org/docs/9.4/external-pl.html > > > Description: > > > > > > At https://www.postgresql.org/docs/9.4/external-pl.html, the link to > PL/Py > > > is broken. Specifically, the link shown is > > > http://python.projects.postgresql.org/backend/, which redirects to > > > http://python.projects.pgfoundry.org/backend/ and returns 404. I > don't know > > > what the correct link should be, if any. > > > > I think PL/Py doesn't exist anymore. > > Some digging turns up that James Pye renamed it to pg-python and moved > to github https://github.com/python-postgres/be but last commit was 4 > years ago to add 9.3 support, so I guess we should just remove it. > > (Meanwhile his Python driver continues to live.) > > -- > Álvaro Herrera https://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services >
