Fix step for using pylint with the Google style guide.

PiperOrigin-RevId: 520886758 Change-Id: I1399258bab93c459b0e7dd5285a4d84a76f917d7
willmcgowan · Apr 17, 2023 · a6d88b6 · a6d88b6
1 parent 77aca74
commit a6d88b6
Showing 1 changed file with 5 additions and 3 deletions.
diff --git a/docs/developer_guide.md b/docs/developer_guide.md
@@ -73,9 +73,11 @@ ideal to first be aware of the general API (see `spiel.h`).
     be clear from the game you copied from. If not, each API function that is
     overridden will be fully documented in superclasses in `spiel.h`.
 8.  Run your code through a linter so it conforms to Google's
-    [style guides](https://google.github.io/styleguide/). For C++ and Python
-    use [cpplint](https://pypi.org/project/cpplint/). There is also
-    [YAPF](https://github.com/google/yapf/) for Python as well.
+    [style guides](https://google.github.io/styleguide/). For C++
+    use [cpplint](https://pypi.org/project/cpplint/). For Python, use
+    [pylint](https://pypi.org/project/pylint/) with the
+    [pylintrc from the Google style guide](https://google.github.io/styleguide/pyguide.html).
+    There is also [YAPF](https://github.com/google/yapf/) for Python as well.
 9.  Once done, rebuild and rerun the tests to ensure everything passes
     (including your new game’s test!).
 10. Add a playthrough file to catch regressions: