From ef0e7fd1d7c557850168052405cce0b7a210f8fa Mon Sep 17 00:00:00 2001 From: "Brutus (robot)" Date: Sun, 4 Jan 2026 20:14:22 +0000 Subject: [PATCH 1/2] Bump rumdl-pre-commit from v0.0.190 to v0.0.208 --- .pre-commit-config.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index a8a3f60..281ab87 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -10,7 +10,7 @@ repos: exclude: "locales" - id: trailing-whitespace - repo: https://github.com/rvben/rumdl-pre-commit - rev: v0.0.190 + rev: v0.0.208 hooks: - id: rumdl args: [] From f357fcba1fdc96cc1a885a1a6c10a0751b313911 Mon Sep 17 00:00:00 2001 From: Kattni Date: Sun, 4 Jan 2026 18:51:01 -0500 Subject: [PATCH 2/2] rumdl fixes. --- docs/en/tutorial/tutorial-8.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/tutorial/tutorial-8.md b/docs/en/tutorial/tutorial-8.md index d9c4e0f..fd59ec6 100644 --- a/docs/en/tutorial/tutorial-8.md +++ b/docs/en/tutorial/tutorial-8.md @@ -193,9 +193,9 @@ async def say_hello(self, widget): There are only three changes to this callback from the previous version: -1. The client that is created is an asynchronous `AsyncClient()`, rather than a synchronous `Client()`. This tells `httpx` that it should operate in asynchronous mode, rather than synchronous mode. -2. The context manager used to create the client is marked as `async`. This tells Python that there is an opportunity to release control as the context manager is entered and exited. -3. The `get` call is made with an `await` keyword. This instructs the app that while we are waiting for the response from the network, the app can release control to the event loop. We've seen this keyword before - we also use `await` when displaying the dialog box. The reason for that usage is the same as it is for the HTTP request - we need to tell the app that while the dialog is displayed, and we're waiting for the user to push a button, it's OK to release control back to the event loop. +1. The client that is created is an asynchronous `AsyncClient()`, rather than a synchronous `Client()`. This tells `httpx` that it should operate in asynchronous mode, rather than synchronous mode. +2. The context manager used to create the client is marked as `async`. This tells Python that there is an opportunity to release control as the context manager is entered and exited. +3. The `get` call is made with an `await` keyword. This instructs the app that while we are waiting for the response from the network, the app can release control to the event loop. We've seen this keyword before - we also use `await` when displaying the dialog box. The reason for that usage is the same as it is for the HTTP request - we need to tell the app that while the dialog is displayed, and we're waiting for the user to push a button, it's OK to release control back to the event loop. It's also important to note that the handler itself is defined as `async def`, rather than just `def`. This tells Python that the method is an asynchronous coroutine. We made this change back in Tutorial 3 when we added the dialog box. You can only use `await` statements inside a method that is declared as `async def`.