| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Subject: | Re: RFC: adding pytest as a supported test framework |
| Date: | 2025-09-18 18:22:48 |
| Message-ID: | CAOYmi+kebAt6wSX7ee0c0kMzV7r0hp93bAt10V5a88yHHUKwog@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 9, 2025 at 2:50 PM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> When enabling the feature, the check_pytest.py script checks that the
> configured `PYTHON` executable has all of pytest-requirements.txt
> installed. Peter pointed out that this is incorrect: what we actually
> want to check is that the interpreter used by pytest has all of the
> required packages, and the two could be different.
Turns out we've already solved this exact problem for Perl and Prove
[1], and I should probably choose a similar solution for Python and
pytest. In other words: make the requirements check into a test.
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2025-09-18 18:33:04 | Re: PG 18 relnotes and RC1 |
| Previous Message | Jonathan S. Katz | 2025-09-18 18:19:42 | Re: PG 18 relnotes and RC1 |