[NFC][Py Reformat] Reformat python files in lldb

This is an ongoing series of commits that are reformatting our Python
code. Reformatting is done with `black` (23.1.0).

If you end up having problems merging this commit because you have made
changes to a python file, the best way to handle that is to run `git
checkout --ours <yourfile>` and then reformat it with black.

RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Differential revision: https://reviews.llvm.org/D151460

1 files changed, 21 insertions, 17 deletions

diff --git a/lldb/test/API/functionalities/recursion/TestValueObjectRecursion.py b/lldb/test/API/functionalities/recursion/TestValueObjectRecursion.py
index 7e8c7cb8952f..a98cf97fd943 100644
--- a/lldb/test/API/functionalities/recursion/TestValueObjectRecursion.py
+++ b/lldb/test/API/functionalities/recursion/TestValueObjectRecursion.py
@@ -9,12 +9,11 @@ import lldbsuite.test.lldbutil as lldbutil
 
 
 class ValueObjectRecursionTestCase(TestBase):
-
     def setUp(self):
         # Call super's setUp().
         TestBase.setUp(self)
         # Find the line number to break at.
-        self.line = line_number('main.cpp', '// Set break point at this line.')
+        self.line = line_number("main.cpp", "// Set break point at this line.")
 
     @no_debug_info_test
     def test_with_run_command(self):
@@ -23,20 +22,23 @@ class ValueObjectRecursionTestCase(TestBase):
         self.runCmd("file " + self.getBuildArtifact("a.out"), CURRENT_EXECUTABLE_SET)
 
         lldbutil.run_break_set_by_file_and_line(
-            self, "main.cpp", self.line, num_expected_locations=1, loc_exact=True)
+            self, "main.cpp", self.line, num_expected_locations=1, loc_exact=True
+        )
 
         self.runCmd("run", RUN_SUCCEEDED)
 
         # The stop reason of the thread should be breakpoint.
-        self.expect("thread list", STOPPED_DUE_TO_BREAKPOINT,
-                    substrs=['stopped',
-                             'stop reason = breakpoint'])
+        self.expect(
+            "thread list",
+            STOPPED_DUE_TO_BREAKPOINT,
+            substrs=["stopped", "stop reason = breakpoint"],
+        )
 
         # This is the function to remove the custom formats in order to have a
         # clean slate for the next test case.
         def cleanup():
-            self.runCmd('type format clear', check=False)
-            self.runCmd('type summary clear', check=False)
+            self.runCmd("type format clear", check=False)
+            self.runCmd("type summary clear", check=False)
 
         # Execute the cleanup function during test case tear down.
         self.addTearDownHook(cleanup)
@@ -50,15 +52,17 @@ class ValueObjectRecursionTestCase(TestBase):
             child = child.GetChildAtIndex(1)
         if self.TraceOn():
             print(child)
+        self.assertTrue(child.IsValid(), "could not retrieve the deep ValueObject")
         self.assertTrue(
-            child.IsValid(),
-            "could not retrieve the deep ValueObject")
-        self.assertTrue(
-            child.GetChildAtIndex(0).IsValid(),
-            "the deep ValueObject has no value")
+            child.GetChildAtIndex(0).IsValid(), "the deep ValueObject has no value"
+        )
         self.assertNotEqual(
-            child.GetChildAtIndex(0).GetValueAsUnsigned(), 0,
-            "the deep ValueObject has a zero value")
+            child.GetChildAtIndex(0).GetValueAsUnsigned(),
+            0,
+            "the deep ValueObject has a zero value",
+        )
         self.assertNotEqual(
-            child.GetChildAtIndex(1).GetValueAsUnsigned(), 0,
-            "the deep ValueObject has no next")
+            child.GetChildAtIndex(1).GetValueAsUnsigned(),
+            0,
+            "the deep ValueObject has no next",
+        )