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 ezgb v2 0/3] Tighten JSON and source type checks
Date: Fri, 18 Sep 2026 18:03:20 -0400 [thread overview]
Message-ID: <20260918-stronger-type-checking-v2-0-3ddc31ba2616@kernel.org> (raw)
Upstream a047342a231d superseded the CI, formatting and checker setup
from v1. These three remaining patches narrow JSON and git objects,
replace the dynamic writer test double with a typed subclass, and enable
strict Pyright checks for source code. They also align the contributor
documentation with the uv-based CI workflow.
The Python 3.10 minimum was already part of v1; this revision also updates
the interpreter matrix and installation documentation to match.
Signed-off-by: Tamir Duberstein <tamird@kernel.org>
Assisted-by: LLM
---
Changes in v2:
- Rebase onto 0.2.0 and drop the CI, formatting and checker setup
covered by a047342a231d.
- Centralize the mutually recursive JSON object/value aliases and
preserve null label and attachment arrays; model null labels in tests.
- Align the interpreter matrix and installation documentation with
the Python 3.10 minimum already introduced in v1.
- Declare typing-extensions for the test double's override decorator
and update uv.lock without upgrading the retained dependencies.
- Update CONTRIBUTING alongside the README development instructions.
- Link to v1: https://patch.msgid.link/20260419-stronger-type-checking-v1-0-222775b987e5@kernel.org
---
Tamir Duberstein (3):
Narrow JSON types and type test doubles
Enable strict pyright source checks
Document local CI checks
CONTRIBUTING.md | 17 +--
README.md | 15 ++-
ci-matrix.sh | 4 +-
docs/installation.rst | 2 +-
pyproject.toml | 16 +--
src/ezgb/__init__.py | 17 ++-
src/ezgb/_models.py | 4 +-
src/ezgb/_reader.py | 190 +++++++++++++++++++--------
src/ezgb/_types.py | 17 +++
tests/conftest.py | 89 ++++++-------
tests/test_ezgb.py | 42 ++++--
tests/test_integration.py | 21 +--
uv.lock | 328 ++++------------------------------------------
13 files changed, 300 insertions(+), 462 deletions(-)
---
base-commit: b6f280f1dc99d57550e92798167c6a16d53ebf57
change-id: 20260419-stronger-type-checking-64a26f72e878
Best regards,
--
Tamir Duberstein <tamird@kernel.org>
next reply other threads:[~2026-09-18 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 22:03 Tamir Duberstein [this message]
2026-09-18 22:03 ` [PATCH ezgb v2 1/3] Narrow JSON types and type test doubles Tamir Duberstein
2026-09-18 22:03 ` [PATCH ezgb v2 2/3] Enable strict pyright source checks Tamir Duberstein
2026-09-18 22:03 ` [PATCH ezgb v2 3/3] Document local CI checks Tamir Duberstein
2026-10-05 10:57 ` [PATCH ezgb v2 0/3] Tighten JSON and source type 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-3ddc31ba2616@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.