From e053bd16c505d4021b3a166603dab6549d4bf2a5 Mon Sep 17 00:00:00 2001 From: David Brochart Date: Thu, 1 Oct 2026 09:38:31 +0200 Subject: [PATCH] PEP 818: Fix typos --- peps/pep-0818.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/peps/pep-0818.rst b/peps/pep-0818.rst index 6eb478744f9..fff7292801a 100644 --- a/peps/pep-0818.rst +++ b/peps/pep-0818.rst @@ -1341,7 +1341,7 @@ is the following implementation of ``call_later()`` which uses the JavaScript The event loop also creates custom futures ``WebFuture`` and ``WebTask``. These are like normal futures and tasks except that they also implement the JavaScript Promise methods ``then()``, ``catch()`` and ``finally_()``. This is so that code -can work consistently regardless of whether they have a ``Promise`` a +can work consistently regardless of whether they have a ``Promise``, a ``WebFuture`` or a ``WebTask``. Adapting from a Python awaitable to a JavaScript awaitable @@ -1374,7 +1374,7 @@ Adapting from a JavaScript awaitable to a Python awaitable The key function here is ``jsawaitable_to_pyawaitable``. Most of the logic in ``jsawaitable_to_pyawaitable`` revolves around the fact that we need to take -care that when when the promise is resolved or rejected, we release both +care that when the promise is resolved or rejected, we release both ``future.set_result()`` and ``future.set_exception()``. When a ``Promise`` is returned from a JavaScript function, we use the ``done_callback`` optional argument to release the Python arguments to the JavaScript function after the