From: Tamir Duberstein <tamird@gmail.com>
To: "Kernel.org Tools" <tools@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Tamir Duberstein <tamird@gmail.com>
Subject: [PATCH v2 13/14] Update README for uv-based dev checks
Date: Mon, 13 Apr 2026 18:08:27 -0400 [thread overview]
Message-ID: <20260413-harden-type-checking-v2-13-1ba6056288d9@gmail.com> (raw)
In-Reply-To: <20260413-harden-type-checking-v2-0-1ba6056288d9@gmail.com>
Document the development workflow in terms of `uv` and mention `pyright`,
`ty check`, and `ruff format`.
Signed-off-by: Tamir Duberstein <tamird@gmail.com>
---
README.md | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/README.md b/README.md
index 3709d7e..1c3863e 100644
--- a/README.md
+++ b/README.md
@@ -613,25 +613,28 @@ except LibloreError:
Install with development dependencies:
```shell
-pip install -e ".[dev]"
+uv sync --all-extras --all-groups
```
Run the test suite:
```shell
-pytest
+uv run --all-extras --all-groups pytest
```
Type checking:
```shell
-mypy src/liblore/ --strict
+uv run --all-extras --all-groups ty check
+uv run --all-extras --all-groups mypy .
+uv run --all-extras --all-groups pyright
```
Linting:
```shell
-ruff check src/liblore/
+uv run --all-extras --all-groups ruff format --check
+uv run --all-extras --all-groups ruff check
```
## Bug Reports
--
2.53.0
next prev parent reply other threads:[~2026-04-13 22:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 22:08 [PATCH v2 00/14] Harden local type checking and test mocking Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 01/14] Add ci script and mypy suppressions Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 02/14] Type make_msg and drop test suppressions Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 03/14] Add ruff import checks to b4 CI Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 04/14] Add ruff format check to CI Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 05/14] Add pyright strict checks " Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 06/14] Replace HTTP session mocks with responses Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 07/14] Add ty checks to CI Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 08/14] Drop redundant read-only property test Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 09/14] Type from_git_config keyword arguments Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 10/14] Add authheaders stub and typed callable Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 11/14] Replace batch mocks with subclasses Tamir Duberstein
2026-04-13 22:08 ` [PATCH v2 12/14] Use CompletedProcess in git config tests Tamir Duberstein
2026-04-13 22:08 ` Tamir Duberstein [this message]
2026-04-13 22:08 ` [PATCH v2 14/14] Add b4 send configuration Tamir Duberstein
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=20260413-harden-type-checking-v2-13-1ba6056288d9@gmail.com \
--to=tamird@gmail.com \
--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