My preference order would be: "black" then "autopep8" then "no change"
Echoing Joris's and Neal's comments I'm a huge fan of having tools fix things for me (and the more it handles the better). Maybe I just need to setup my editor better to deal with PEP8 issue but I find I spend more time then I would want making the linter happy, so any automation is better then none. For reference 2600 lines additions in Black is about 7% addition to the code base. I find most of these make it easier to read (but I haven't been doing a lot of python programming lately). The one thing that looks ugly, but i would guess fade over time is placing closing braces on there own line in some cases. Would starting with autopep8 and see if linting is still a pain point, then reconsider black? Thanks, Micah On Thu, Apr 9, 2020 at 10:36 AM Joris Van den Bossche < jorisvandenboss...@gmail.com> wrote: > > > So autopep8 doesn't fix everything? Sounds inferior to me. That said, > I'm > > > in favor of any resolution that increases our automation of this and > > > decreases the energy we expend debating it. > > > > It does fix everything, where "everything" is compliance with PEP8, > > which I think is the thing we are most interested in. > > > > Note that autopep8 does not fix everything, even for PEP8 compliance. > At least, it can often not automatically fix "too long line length" for > code lines (that was actually the trigger for me to start the thread about > adopting black). >
