Page MenuHomePhabricator

style: drop requirement to only use single lines between top-level objects

Authored by mjpieters on Oct 14 2018, 9:41 AM.

Diff Detail

rHG Mercurial
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

mjpieters created this revision.Oct 14 2018, 9:41 AM
durin42 accepted this revision as: durin42.Oct 14 2018, 11:35 AM
durin42 added a subscriber: durin42.

I'm in favor, but want to see a broader set of thoughts on this.

indygreg accepted this revision.Oct 16 2018, 3:52 AM

At the 4.8 sprint, we agreed to repo mass rewriting with style that is more PEP-8 like. The tentative plan is to use black, which is very opinionated and doesn't give us much room for style flexibility. But regardless if we do that, I distinctly remember us saying we wanted to adopt double newline between module elements, allowing _ in names, and using CamelCase for class names. The former would be added automatically by black. The latter 2 would lead to inconsistent style in the long term, which we're OK with.

Since we agreed to allow double newlines and this patch formalizes that policy decision, I'm taking it. (I would also accept patches that removes the bit that complains about new symbols using _ and uppercase in names.)

This revision is now accepted and ready to land.Oct 16 2018, 3:52 AM
This revision was automatically updated to reflect the committed changes.