[Pandas-dev] PDEPs: pandas enhancement proposals

[Joris Van den Bossche]

Thanks for starting this proposal, Marc!

I have already been doing this in some ad-hoc way with eg the Copy/View
proposal (writing an actual proposal document), so I am very much in favor
of formalizing this a bit more.

Personally, I would prefer that we use a more dedicated home for this
instead of using the existing pandas repo (e.g. a separate repo in the
pandas-dev org). The main pandas repo has nowadays such a high volume in
issue and PR comments, that it becomes difficult to follow this or notice
specific issues. While there are certainly ways to deal with this (e.g.
consistently using a specific label and title, ensuring we always notify
the mailing list as well, ...), IMO it would make it more accessible to
follow and have an overview of those discussions in e.g. a separate repo.

(there are examples of both in other projects, for example scikit-learn has
a separate repo, while bumpy uses the main repo I think)

Joris

Op di 21 jun. 2022 09:46 schreef Marc Garcia <garcia.marc at gmail.com>:

> We're in the process of implementing PDEPs, equivalent to Python's PEPs
> and NumPy's NEPs, but for pandas. This should help build the roadmap, make
> discussions more efficient, obtain more structured feedback from the
> community, and add visibility to agreed future plans for pandas.
>
> The initial implementation (workflow) is a bit simpler than PEP or NEP,
> but we'll iterate in the future as convenient.
>
> You can see the PR for PDEP-1 with the purpose, scope and guidelines here:
> https://github.com/pandas-dev/pandas/pull/47444
>
> Feedback is very welcome.
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pandas-dev/attachments/20220624/4f4c9f5d/attachment.html>