gdb: re-format Python files using black 21.4b0

Re-format all Python files using black [1] version 21.4b0.  The goal is
that from now on, we keep all Python files formatted using black.  And
that we never have to discuss formatting during review (for these files
at least) ever again.

One change is needed in gdb.python/py-prettyprint.exp, because it
matches the string representation of an exception, which shows source
code.  So the change in formatting must be replicated in the expected
regexp.

To document our usage of black I plan on adding this to the "GDB Python
Coding Standards" wiki page [2]:

--8<--

All Python source files under the `gdb/` directory must be formatted
using black version 21.4b0.

This specific version can be installed using:

    $ pip3 install 'black == 21.4b0'

All you need to do to re-format files is run `black <file/directory>`,
and black will re-format any Python file it finds in there.  It runs
quite fast, so the simplest is to do:

    $ black gdb/

from the top-level.

If you notice that black produces changes unrelated to your patch, it's
probably because someone forgot to run it before you.  In this case,
don't include unrelated hunks in your patch.  Push an obvious patch
fixing the formatting and rebase your work on top of that.

-->8--

Once this is merged, I plan on setting a up an `ignoreRevsFile`
config so that git-blame ignores this commit, as described here:

  https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame

I also plan on working on a git commit hook (checked in the repo) to
automatically check the formatting of the Python files on commit.

[1] https://pypi.org/project/black/
[2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards

gdb/ChangeLog:

	* Re-format all Python files using black.

gdb/testsuite/ChangeLog:

	* Re-format all Python files using black.
	* gdb.python/py-prettyprint.exp (run_lang_tests): Adjust.

Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919

1 files changed, 8 insertions, 8 deletions

diff --git a/gdb/testsuite/gdb.python/py-pp-registration.py b/gdb/testsuite/gdb.python/py-pp-registration.py
index edf58ca..f34936e 100644
--- a/gdb/testsuite/gdb.python/py-pp-registration.py
+++ b/gdb/testsuite/gdb.python/py-pp-registration.py
@@ -27,8 +27,7 @@ def lookup_function_lookup_test(val):
             self.val = val
 
         def to_string(self):
-            return ("x=<" + str(self.val["x"]) +
-                    "> y=<" + str(self.val["y"]) + ">")
+            return "x=<" + str(self.val["x"]) + "> y=<" + str(self.val["y"]) + ">"
 
     typename = gdb.types.get_basic_type(val.type).tag
     # Note: typename could be None.
@@ -37,7 +36,7 @@ def lookup_function_lookup_test(val):
     return None
 
 
-class pp_s1 (object):
+class pp_s1(object):
     def __init__(self, val):
         self.val = val
 
@@ -47,7 +46,7 @@ class pp_s1 (object):
         return "s1 a=<" + str(self.val["a"]) + "> b=<" + str(self.val["b"]) + ">"
 
 
-class pp_s2 (object):
+class pp_s2(object):
     def __init__(self, val):
         self.val = val
 
@@ -60,8 +59,8 @@ class pp_s2 (object):
 def build_pretty_printer1():
     pp = gdb.printing.RegexpCollectionPrettyPrinter("pp-test")
 
-    pp.add_printer('struct s', '^struct s$', pp_s1)
-    pp.add_printer('s', '^s$', pp_s1)
+    pp.add_printer("struct s", "^struct s$", pp_s1)
+    pp.add_printer("s", "^s$", pp_s1)
 
     return pp
 
@@ -72,9 +71,10 @@ def build_pretty_printer2():
     # register_pretty_printer.
     pp = gdb.printing.RegexpCollectionPrettyPrinter("pp-test")
 
-    pp.add_printer('struct s', '^struct s$', pp_s2)
-    pp.add_printer('s', '^s$', pp_s2)
+    pp.add_printer("struct s", "^struct s$", pp_s2)
+    pp.add_printer("s", "^s$", pp_s2)
 
     return pp
 
+
 # Note: Registering the printers is done in the .exp file.