Request: Leadership, please put resources into this project

[LuminairPrime]

I just got here and the Issues section looks like the side of a road. 46% of all YAPF issues remain open. Black has more than twice as many issues, but only 16% are open. It's clear that leadership has neglected this project. I've barely seen reference to YAPF in other Google project documentation, so maybe the project is just dead and everybody has moved to Black, which does have over 2x more contributors, users, and GitHub stars.

My request is: Whoever's holding the keys to this account at Google needs to put somebody on reading the issues section. Or add a Black style option and close up shop.

[kamahen]

As the README.md says:
"YAPF is not an official Google product (experimental or otherwise), it is just code that happens to be owned by Google."

Of course, YAPF has more open issues than Black -- most of issues are requests for more knobs to tweak the output. Black explicitly doesn't have such knobs.

I, for one, am grateful to @gwelymernans for all the volunteer work he has put into this project - it's not part of his official duties at Google.

[bwendling]

Thanks, @kamahen.

Unfortunately, I've had less time to put into YAPF over the years. I had hope more people would be interested in contributing to YAPF, but few have done more than a couple of patches here and there.

The main issue with YAPF is its reliance on lib2to3 as its parser, which is going away and isn't very sustainable anyway. I created a new parser to replace it, but completing it (e.g. getting the penalties correct) a very large project.

Because of the "lack of time" issue and the lack of contributors, it might be best to go with Black. I hear only good things about it.

[kamahen]

@gwelymernans - Is this #993 and 516e197 ?

I think that pytype is switching to LibCST (possibly Black is also switching to LibCST, but I haven't been tracking that)

[jni]

Hi folks,

Thank you for all the work you've done with yapf so far. I've seen here and in #993 mentions of a new parser (from two different Bill Wendlings 😂), but it's not clear to me whether they've gone or will go anywhere. Are there any WIP branches around? I will say that I personally much prefer yapf to black, indeed because of its knobs, which make it easier to get nice formatting for scientific computing (e.g. dealing with operator priority), among other things (I for one like an extra indent for line continuations). And I would be very sad to see it die and have black become the only game in town.

I don't really have anything else to offer other than a rebuke of "I hear only good things about it." 😉 Thank you again, I'm not sure if verbal support helps, but I hope it does. And I hope even more that it motivates someone new to pick up the threads of the new parsers! 🤞