Unstable formatting with long not in clause

[Zac-HD]

Black v20.8b1, repro at this playground link

if "a" not in ("AAAAAAAAAAAAAAAAAAAAAAAAAA", "BBBBBBBBBBBBBBBBBBBBBBBBBBBBB") or "b" in ("A", "B"):
    pass

INTERNAL ERROR: Black produced different code on the second pass of the formatter.
Mode(target_versions=set(), line_length=88, string_normalization=True, experimental_string_processing=False, is_pyi=False)
--- source
+++ first pass
@@ -1,2 +1,5 @@
-if "a" not in ("AAAAAAAAAAAAAAAAAAAAAAAAAA", "BBBBBBBBBBBBBBBBBBBBBBBBBBBBB") or "b" in ("A", "B"):
+if "a" not in (
+    "AAAAAAAAAAAAAAAAAAAAAAAAAA",
+    "BBBBBBBBBBBBBBBBBBBBBBBBBBBBB",
+) or "b" in ("A", "B"):
     pass
--- first pass
+++ second pass
@@ -1,5 +1,9 @@
-if "a" not in (
-    "AAAAAAAAAAAAAAAAAAAAAAAAAA",
-    "BBBBBBBBBBBBBBBBBBBBBBBBBBBBB",
-) or "b" in ("A", "B"):
+if (
+    "a"
+    not in (
+        "AAAAAAAAAAAAAAAAAAAAAAAAAA",
+        "BBBBBBBBBBBBBBBBBBBBBBBBBBBBB",
+    )
+    or "b" in ("A", "B")
+):
     pass

For what it's worth I think the first-pass format is nicer, but I don't really care so long as it's autoformatted 😁

[mvolfik]

Works with #1958, so likely a duplicate of #1629

[ichard26]

Hello!

All reproduction cases in this issue format without error on master. The fixing commit was 8672af3 from PR GH-2126. I'll be marking this issue as a duplicate of GH-1629 since that's what GH-2126 aimed to fix and it's highly likely this issue falls under GH-1629.

Since we use the issue tracker as a reflection of what's on master, I'll be closing this issue. If you have any issues, especially with the new (but stable) output, please open a new issue. Oh and the fix should be available in a published release soon, see GH-2125 for more info.

Thank you for reporting!