Am Freitag, den 25.09.2020, 21:14 +0200 schrieb Jean Abou Samra: > Le 25/09/2020 à 16:39, Jonas Hahnfeld a écrit : > > > Am Freitag, den 25.09.2020, 16:01 +0200 schrieb Jean Abou Samra: > > > Le 25/09/2020 à 15:48, Jonas Hahnfeld a écrit : > > > > Anyway, running black on all Python files gives the following error: > > > > > > > > error: cannot format > > > > /code/LilyPond/src/scripts/auxiliar/translations-status.py: INTERNAL > > > > ERROR: Black produced different code on the second pass of the > > > > formatter. > > > > > > I can't reproduce this. What is your version of Black? (Mine is > > > 19.3b0.) What line length did you use? > > > > > > The latest, 20.8b1. Happens with both the default and -l 78. > > Seems to be a known, recently introduced bug in Black.It's easy > to work around it using --fast.
This will just skip the sanity check that future runs keep the formatting. I don't consider this a valid workaround because we *will* run the tool again later on. Jonas
signature.asc
Description: This is a digitally signed message part
