D6342: style: run a patched black on a subset of mercurial

Augie Fackler raf at durin42.com
Mon May 6 14:26:08 EDT 2019

Yes, the intent is to show what the result of the patch to black is,
and once that lands to try and get consensus that we've addressed the
major issue with black and can move on. I've tried adding b prefixes
everywhere without black, or by using a different formatter, and the
other formatters just aren't good enough at wrapping lines, so not
using black will probably imply some kind of pain. :(

On Mon, May 6, 2019 at 12:01 PM martinvonz (Martin von Zweigbergk)
<phabricator at mercurial-scm.org> wrote:
> martinvonz added a comment.
>   I would be happy to have our code auto-formatted. I assume this patch is just to show what the result will be and it's not meant to be queued until that patch for black has been accepted.
> > policy.py:27-30
> > +    b"c": (
> > +        r"cext",
> > +        None,
> > +    ),
> As I said on the pull request for black, I don't like that these lines get split up.
>   rHG Mercurial
>   https://phab.mercurial-scm.org/D6342
> To: durin42, #hg-reviewers
> Cc: martinvonz, mjpieters, mercurial-devel
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

More information about the Mercurial-devel mailing list