MIME-Version: 1.0
References: <CAOYmi+kThkM9Z87u=R_Wi7fCor2i+UZKAyq0UCyprzCwTQvqgA@mail.gmail.com>
 <20240610200411.byj6sv2vpgol6wcf@awork3.anarazel.de> <CAOYmi+niQdwFdX7srOiD8zdme_rxEp2m4JGdqzK=+dS6dpV2Og@mail.gmail.com>
 <20240612155040.u6cvatdb5tiwcxci@awork3.anarazel.de> <FAC2FCFE-8C70-4996-9598-34DD7596BB41@yesql.se>
 <CA+Tgmobhsqh8c+ySXaPf5MdVwFYW6ceQ05N7pav6dzecxJGJoQ@mail.gmail.com>
 <CAGECzQTtGoPGQMZactCAytbPvNcA59Zk7RA7SEmzObyAm7K=5w@mail.gmail.com>
 <CA+TgmoZCQtUu4u7XJ1umD8k5pTuM3h2zLDyQ1uoVOP-==gJz_Q@mail.gmail.com>
 <CAGECzQTzjVaMrKi5SCqL+H63pOx8r1DP0JpJ0v2SfaE0fMaNmg@mail.gmail.com>
 <CAKAnmmJABbqnWDGQShnpnSUmssBrK4Y1b0O1gWWjRF7=yR=U9w@mail.gmail.com> <CAGECzQTu6knBYsCDi20Z+ezD_3F-g38Aq7u7ctPBmFqKE=ZvAw@mail.gmail.com>
In-Reply-To: <CAGECzQTu6knBYsCDi20Z+ezD_3F-g38Aq7u7ctPBmFqKE=ZvAw@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Sat, 15 Jun 2024 17:57:29 -0400
Message-ID: <CAKAnmm+NHC3xn_ZavrhH1GaJ5ts=GVKtxTpuN74dEUjiovrLCA@mail.gmail.com>
Subject: Re: RFC: adding pytest as a supported test framework
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Robert Haas <robertmhaas@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, 
	Andres Freund <andres@anarazel.de>, Jacob Champion <jacob.champion@enterprisedb.com>, 
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000aa68a4061af4d3b8"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2BNHC3xn_ZavrhH1GaJ5ts%3DGVKtxTpuN74dEUjiovrLCA%40mail.gmail.com>
Precedence: bulk

--000000000000aa68a4061af4d3b8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 14, 2024 at 5:09=E2=80=AFPM Jelte Fennema-Nio <postgres@jeltef.=
nl>
wrote:

> Test::More on the other hand, while indeed still maintained, it's
> definitely not getting significant new feature development or
> improvements[2]. Especially when comparing it to pytest[3].
>

That's fair, although it's a little hard to tell if the lack of new
features is because they are not needed for a stable, mature project, or
because few people are asking for and developing new features. Probably a
bit of both. But I'll be the first to admit Perl is dying; I just don't
know what should replace it (or how - or when). Python has its quirks, but
all languages do, and your claim that it will encourage more and easier
test writing by developers is a good one.

Cheers,
Greg

--000000000000aa68a4061af4d3b8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jun 14, 2024 at 5:09=E2=80=AFPM J=
elte Fennema-Nio &lt;<a href=3D"mailto:postgres@jeltef.nl">postgres@jeltef.=
nl</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">Test::More on the other hand, while indeed sti=
ll maintained, it&#39;s<br>
definitely not getting significant new feature development or<br>
improvements[2]. Especially when comparing it to pytest[3].<br></blockquote=
><div><br></div><div>That&#39;s fair, although it&#39;s a little hard to te=
ll if the lack of new features is because they are not needed for a stable,=
 mature project, or because few people are asking for and developing new fe=
atures. Probably a bit of both. But I&#39;ll be the first to admit Perl is =
dying; I just don&#39;t know what should replace it (or how - or when). Pyt=
hon has its quirks, but all languages do, and your claim that it will encou=
rage more and easier test writing by developers is a good one.</div><div><b=
r></div><div>Cheers,</div><div>Greg</div><div>=C2=A0</div></div></div>

--000000000000aa68a4061af4d3b8--