public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>, Tom Tromey <tom@tromey.com>
Subject: [PATCH v3 05/10] gdb: pyproject.toml: set pyright typeCheckingMode = "strict"
Date: Sun, 26 Feb 2023 20:13:58 -0500	[thread overview]
Message-ID: <20230227011403.612304-6-simon.marchi@polymtl.ca> (raw)
In-Reply-To: <20230227011403.612304-1-simon.marchi@polymtl.ca>

While working on other projects, I found the pyright type checker very
helpful when editing Python code.  I don't think I have to explain the
advantages of type checking to a crowd used to C/C++.

Setting typeCheckingMode to "strict" makes pyright flag a bit more type
issues than the default of "basic".

Change-Id: I38818ec59f7f73c2ab020cc9226286cdd485abc7
Reviewed-By: Tom Tromey <tom@tromey.com>
---
 gdb/pyproject.toml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gdb/pyproject.toml b/gdb/pyproject.toml
index 58ed2f9d5564..4469f1cd61df 100644
--- a/gdb/pyproject.toml
+++ b/gdb/pyproject.toml
@@ -1,2 +1,5 @@
 [tool.black]
 include = "\\.py(\\.in)?$"
+
+[tool.pyright]
+typeCheckingMode = "strict"
-- 
2.39.2


  parent reply	other threads:[~2023-02-27  1:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27  1:13 [PATCH v3 00/10] Add typing annotations to gdbarch*.py and make-target-delegates.py Simon Marchi
2023-02-27  1:13 ` [PATCH v3 01/10] gdb: remove invalid / dead code from gdbarch.py Simon Marchi
2023-02-27  1:13 ` [PATCH v3 02/10] gdb: reformat Python files with black 23.1.0 Simon Marchi
2023-02-27  1:13 ` [PATCH v3 03/10] gdb: gdbarch.py: spell out parameters of _Component.__init__ Simon Marchi
2023-02-27  1:13 ` [PATCH v3 04/10] gdb: gdbarch.py: remove Info.__init__ Simon Marchi
2023-02-27  1:13 ` Simon Marchi [this message]
2023-02-27  1:13 ` [PATCH v3 06/10] gdb: split gdbarch component types to gdbarch_types.py Simon Marchi
2023-02-27  1:14 ` [PATCH v3 07/10] gdb: gdbarch*.py, copyright.py: add type annotations Simon Marchi
2023-02-27  1:14 ` [PATCH v3 08/10] gdb: make-target-delegates.py: make one string raw Simon Marchi
2023-02-27  1:14 ` [PATCH v3 09/10] gdb: make-target-delegates.py: add Entry type Simon Marchi
2023-02-27  1:14 ` [PATCH v3 10/10] gdb: make-target-delegates.py: add type annotations Simon Marchi
2023-02-27 17:38 ` [PATCH v3 00/10] Add typing annotations to gdbarch*.py and make-target-delegates.py Andrew Burgess
2023-02-27 18:27   ` Simon Marchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230227011403.612304-6-simon.marchi@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).