From: Vincent Fazio <vfazio@gmail.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [libgpiod][PATCH 9/9] bindings: python: update linter configuration
Date: Fri, 3 Apr 2026 08:09:27 -0500 [thread overview]
Message-ID: <CAOrEah4tpwLkWXbf++na4QUT8--fBT_9_-SkaBL-bmzPV_XhMQ@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=Me286zYriFV-nFNV7K052RAe8H32CjZXbig2cmny7gNXw@mail.gmail.com>
On Fri, Apr 3, 2026 at 4:02 AM Bartosz Golaszewski <brgl@kernel.org> wrote:
>
> I do run them but don't necessarily want them as a commit hook since
> not everyone is working on python side of libgpiod.
There are tools like pre-commit [0] and prek [1] that can trigger
specific actions based on what in the tree is being modified and file
type if that's something you're interested in.
>
> I queued the patches, thanks! I have to say: it's crazy how much
> faster ruff is compared to mypy.
mypy (at least the compiled version) is not too bad when it has a
cache built up since it can do incremental comparisons.
There are alternatives like ty and zuban that are written in rust but
mypy is the reference implementation and not all tools have the same
comprehensive checks, though there is evidence [2] that I may be
operating on old information.
[0]: https://github.com/pre-commit/pre-commit
[1]: https://github.com/j178/prek
[2]: https://htmlpreview.github.io/?https://github.com/python/typing/blob/main/conformance/results/results.html
next prev parent reply other threads:[~2026-04-03 13:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 0:14 [libgpiod][PATCH 1/9] bindings: python: build_tests: do not fallback to distutils Vincent Fazio
2026-04-01 0:14 ` [libgpiod][PATCH 2/9] bindings: python: build_tests: simplify the Distribution Vincent Fazio
2026-04-01 0:14 ` [libgpiod][PATCH 3/9] bindings: python: setup: add type annotations Vincent Fazio
2026-04-01 0:14 ` [libgpiod][PATCH 4/9] bindings: python: setup: apply linter recommendations Vincent Fazio
2026-04-01 0:14 ` [libgpiod][PATCH 5/9] bindings: python: setup: use logging module Vincent Fazio
2026-04-01 0:14 ` [libgpiod][PATCH 6/9] bindings: python: examples: add type annotations Vincent Fazio
2026-04-01 0:14 ` [libgpiod][PATCH 7/9] bindings: python: examples: apply linter recommendations Vincent Fazio
2026-04-01 0:14 ` [libgpiod][PATCH 8/9] bindings: python: add a lint dependency group Vincent Fazio
2026-04-01 0:14 ` [libgpiod][PATCH 9/9] bindings: python: update linter configuration Vincent Fazio
2026-04-02 14:37 ` Bartosz Golaszewski
2026-04-02 15:55 ` Vincent Fazio
2026-04-02 16:42 ` Bartosz Golaszewski
2026-04-02 17:01 ` Vincent Fazio
2026-04-03 9:02 ` Bartosz Golaszewski
2026-04-03 13:09 ` Vincent Fazio [this message]
2026-04-03 9:01 ` [libgpiod][PATCH 1/9] bindings: python: build_tests: do not fallback to distutils Bartosz Golaszewski
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=CAOrEah4tpwLkWXbf++na4QUT8--fBT_9_-SkaBL-bmzPV_XhMQ@mail.gmail.com \
--to=vfazio@gmail.com \
--cc=brgl@kernel.org \
--cc=linux-gpio@vger.kernel.org \
/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).