This is a good idea, and for new code in Airflow I usually use black. However, I agree with Ash that this can make cherrypicking harder even if we run black on v1-10-test branch (there are already differences in code). Personally I would be in favor of introducing black and other things (i.e. pyupgrade) when releasing 2.0.
Regarding the issue of merge conflict in PR - we will not be able to avoid it (however running black locally before rebase should help I think). Cheers, Tomek On Sun, Jun 28, 2020 at 12:51 AM Ash Berlin-Taylor <[email protected]> wrote: > > Yes, to Black in principle. But (and this is a big but) no, not yet. Or not > without testing how it affects our ability to cherry pick back to the release > branch. > > (My default would be to assume it makes them harder/almost impossible and > this should be the almost last thing we do before we release 2.0) > > -ash > > On 27 June 2020 22:02:41 BST, Philippe Gagnon <[email protected]> wrote: > >It's a good idea. > > > >It will make reading the codebase easier, and besides the whole Python > >ecosystem is slowly moving towards adopting this code style. I > >personally > >have been a fan ever since the project launched. > > > >With regards to open PRs requiring a rebase, it's an annoyance for sure > >but > >if we do decide to standardize on any code style (which we should, > >black or > >not), we'll have to pull the bandaid eventually. > > > >Just my two cents. ;-) > > > >Philippe > > > >On Sat, Jun 27, 2020 at 4:13 PM Kaxil Naik <[email protected]> wrote: > > > >> Hi all, > >> > >> I would like to open the discussion to enable Black ( > >> https://github.com/psf/black) - *The Uncompromising Code Formatter* > >for > >> automatic formatting of Airflow's entire codebase. > >> > >> I have created a WIP PR at > >https://github.com/apache/airflow/pull/9550 > >> > >> Some of the caveats: > >> > >> - All the currently open PRs would have some kind of conflict > >errors > >> - It *might *make backporting harder (but should be ok'ish if we > >enable > >> black on v1-10-test but not 100%) > >> - There are known issues with "line-lengths" not being honoured by > >black > >> (https://github.com/psf/black/issues/1161) and the workaround is > >to use > >> "#fmt: off". > >> > >> I would love to hear what the community thinks about it. > >> > >> Regards, > >> Kaxil > >> -- Tomasz Urbaszek Polidea | Software Engineer M: +48 505 628 493 E: [email protected] Unique Tech Check out our projects!
