Re: doc: virtual envs with Pl/Python - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: doc: virtual envs with Pl/Python
Date
Msg-id CAOYmi+k3byW3oUdd5W7EM9zrXZmAWDskMMDurc5VasJ6ZxqB9g@mail.gmail.com
Whole thread Raw
In response to Re: doc: virtual envs with Pl/Python  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Oct 17, 2024 at 2:03 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> What I'm still confused about is whether this is anything that
> a typical user of Python shouldn't be expected to know already.

I mean... I think I agree, but also it seems like people regularly
find ways to shoot themselves in the foot, so I'm not opposed to some
tips in theory. But they should be more generally applicable IMO.

> I understand the idea of setting up a virtualenv that is decoupled
> from the system-supplied package set, but if the user has done
> that, wouldn't they already know about setting PYTHONPATH?

Agreed.

> I can believe that they might not be totally clear on how to
> set it in a way that will affect the Postgres server --- but
> the proposed patch provides no details about that, and hardly
> could since it'd vary so much from one server packaging to
> another.

Yeah. I think this patch is _way_ too prescriptive, and maybe belongs
in a wiki on "Ways I Get Complex Python Setups Working" or similar,
where it can share space with alternatives.

--Jacob



pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: Avoiding superfluous buffer locking during nbtree backwards scans
Next
From: Corey Huinker
Date:
Subject: Re: Soft errors and ThrowErrorData() comment updates