From: Tamir Duberstein <tamird@kernel.org>
To: "Kernel.org Tools" <tools@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Tamir Duberstein <tamird@kernel.org>
Subject: [PATCH patatt v2 0/4] Harden local checks
Date: Fri, 18 Sep 2026 15:02:51 -0400 [thread overview]
Message-ID: <20260918-stronger-type-checking-v2-0-37de1d8a6c86@kernel.org> (raw)
The CI and checker setup proposed in v1 is now largely covered by
05c5bbb0b00e ("Add CI helper scripts and stricter type/lint gates").
This revision builds on that work, retaining the remaining typing and
cleanup changes and adding a lockfile for reproducible checks.
Signed-off-by: Tamir Duberstein <tamird@kernel.org>
---
Changes in v2:
- Rebase onto 0.8.0 and drop the superseded CI, Ruff import/format, and
ty setup patches.
- Add uv.lock in a separate first patch, then upgrade Ruff and ty
alongside the corresponding lint and type fixes.
- Adapt the remaining typing changes to the upstream configuration,
removing unknown-type exemptions and precisely typing the key cache.
- Fix Python 3.8 packaging and test-collection failures and add
regression coverage for cache reuse and missing-key validation.
- Retain the dictionary-lookup and unconditional PyNaCl-import cleanups,
adjusted for upstream changes.
- Link to v1: https://patch.msgid.link/20260419-stronger-type-checking-v1-0-5c108048d2c7@kernel.org
---
Tamir Duberstein (4):
Track uv.lock for reproducible checks
Tighten local type and lint checks
Reduce dictionary lookups
Import PyNaCl unconditionally
.gitignore | 1 -
docs/conf.py | 2 +-
pyproject.toml | 20 +-
src/patatt/__init__.py | 373 ++++----
tests/conftest.py | 12 +-
tests/test_validation.py | 19 +-
tests/unit/test_devsig_header.py | 17 +-
tests/unit/test_get_config_from_git.py | 2 +
tests/unit/test_patatt_message.py | 4 +-
tests/unit/test_run_command.py | 5 +-
uv.lock | 1515 ++++++++++++++++++++++++++++++++
11 files changed, 1753 insertions(+), 217 deletions(-)
---
base-commit: 274198d9d5cc315c9588bf84cc7b53a7261726e4
change-id: 20260419-stronger-type-checking-3702559acba9
Best regards,
--
Tamir Duberstein <tamird@kernel.org>
next reply other threads:[~2026-09-18 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 19:02 Tamir Duberstein [this message]
2026-09-18 19:02 ` [PATCH patatt v2 1/4] Track uv.lock for reproducible checks Tamir Duberstein
2026-09-18 19:02 ` [PATCH patatt v2 2/4] Tighten local type and lint checks Tamir Duberstein
2026-09-18 19:02 ` [PATCH patatt v2 3/4] Reduce dictionary lookups Tamir Duberstein
2026-09-18 19:02 ` [PATCH patatt v2 4/4] Import PyNaCl unconditionally Tamir Duberstein
2026-10-05 10:46 ` [PATCH patatt v2 0/4] Harden local checks Konstantin Ryabitsev
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=20260918-stronger-type-checking-v2-0-37de1d8a6c86@kernel.org \
--to=tamird@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@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