This discussion and the linked gist may be of some help:
https://github.com/scikit-learn/scikit-learn/issues/11336
On Mon, Nov 22, 2021 at 12:02 PM Andrew Nelson wrote:
> Is there a way to figure out which files are not touched by any open PR?
> That way numpy might be able to do a lot more than
Hey all,
If you've ever tried to inspect a file on github with the `.rst`
extension, there's a good chance that you were frustrated by GitHub
providing a rendered view *only* of the file, with no option to view
the source code like any other text file. It is certainly nice to
have a rendered vie
Is there a way to figure out which files are not touched by any open PR?
That way numpy might be able to do a lot more than an incremental code
alignment.
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to num
I think some of the pain points raised here regarding massive churn on
existing PRs & conflicts would be addressed by what Ralf said a few
emails ago:
> A detailed proposal with an incremental formatter may have a chance
here (xref `darker` and our `tools/linter.py`), a "let's just run black"
one
On 18/11/2021 19:07, Stefan van der Walt wrote:
if we do this, we should probably go through each of the 200+ open PRs (or, at
least, the non-conflicted ones), apply the formatter, and then squash the PR
into a single commit. We can do that by script.
We had to deal with this issue in scikit-
