On Wed, 7 Jan 2026 at 00:17, Andres Freund <andres@anarazel.de> wrote:
> I'm somewhat sceptical that the .venv support should be introduced together
> with the rest of this.
Could you expand a bit on this? My thinking was that people have a
tendency to get confused by python dependency management (because
there's too many options to do it). So having an easy documented and
supported way to do it seemed like a good idea to have people not get
frustrated.
Would you rather have it only be documented how to install the python
dependencies? And not have meson/autoconf automatically detect the
.venv?
To be clear, if it was only pytest then recommending "pipx install
pytest" would probably be easiest, but it seems like we'll at least
want cryptography for the tests Jacob is writing.
And I'm also thinking ahead a bit towards being able to use (a
specific version of) ruff for formatting & linting of python code. See
also[1]
[1]: https://www.postgresql.org/message-id/flat/DFCDD5H4J7VX.3GJKRBBDCKQ86@jeltef.nl
