[Lldb-commits] [lldb] [lldb/Commands] Alias `script` command to `scripting execute` (PR #97263)

via lldb-commits lldb-commits at lists.llvm.org
Mon Jul 1 11:58:17 PDT 2024


github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {darker}-->


:warning: Python code formatter, darker found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
darker --check --diff -r a9c12e481bfef5b2913e2241486f4dd450188cd2...1f3d0498ccedc4c8adef01d44c29be8b1a78b133 lldb/test/API/functionalities/abbreviation/TestAbbreviations.py
``````````

</details>

<details>
<summary>
View the diff from darker here.
</summary>

``````````diff
--- TestAbbreviations.py	2024-07-01 18:53:49.000000 +0000
+++ TestAbbreviations.py	2024-07-01 18:57:53.107299 +0000
@@ -78,11 +78,13 @@
         self.assertFalse(result.Succeeded())
 
         # Check a command that wants the raw input.
         command_interpreter.ResolveCommand(r"""sc print("\n\n\tHello!\n")""", result)
         self.assertTrue(result.Succeeded())
-        self.assertEqual(r"""scripting execute print("\n\n\tHello!\n")""", result.GetOutput())
+        self.assertEqual(
+            r"""scripting execute print("\n\n\tHello!\n")""", result.GetOutput()
+        )
 
         # Prompt changing stuff should be tested, but this doesn't seem like the
         # right test to do it in.  It has nothing to do with aliases or abbreviations.
         # self.runCmd("com sou ./change_prompt.lldb")
         # self.expect("settings show prompt",

``````````

</details>


https://github.com/llvm/llvm-project/pull/97263


More information about the lldb-commits mailing list