Some automation could be done for adding new packages to already existing PRs,
where correct addition would integrate nicely, align stats, such as last
update, stack trends, benchmarks
> On 2 Jul 2023, at 09:36, Christopher Barker wrote:
>
> On Sat, Jul 1, 2023 at 11:01 PM Chris Angelico
On Sun, 2 Jul 2023 at 06:11, Christopher Barker wrote:
>
> The OP of this thread is not alone -- folks want an authoritative source
>
Authority is built over time. Unless someone starts doing this, there will
never be any authoritative source. In case it’s not obvious, none of the
projects or gr
On 2023-07-02 06:59, Chris Angelico wrote:
On Sun, 2 Jul 2023 at 15:48, Christopher Barker wrote:
Only re (the one in the stdlib)? What if you want PCREs -
there's no package called "pcre" but there's "pcre2", "python-pcre",
and probably others.
And are those three (and others?) actually use
MRAB writes:
> I would hope that if the maintainer knew that the package was on
> the curated list, they would let the list know if they were going
> to stop maintaining it. That would be part of being on the list -
> informing the list's maintainers of any significant change of
> status.
Ho
On 2023-07-02 17:14, Stephen J. Turnbull wrote:
MRAB writes:
> I would hope that if the maintainer knew that the package was on
> the curated list, they would let the list know if they were going
> to stop maintaining it. That would be part of being on the list -
> informing the list's m