aboutsummaryrefslogtreecommitdiffstats
path: root/examples/async/eratosthenes/doc/eratosthenes.rst
diff options
context:
space:
mode:
Diffstat (limited to 'examples/async/eratosthenes/doc/eratosthenes.rst')
-rw-r--r--examples/async/eratosthenes/doc/eratosthenes.rst42
1 files changed, 42 insertions, 0 deletions
diff --git a/examples/async/eratosthenes/doc/eratosthenes.rst b/examples/async/eratosthenes/doc/eratosthenes.rst
new file mode 100644
index 000000000..37758e99f
--- /dev/null
+++ b/examples/async/eratosthenes/doc/eratosthenes.rst
@@ -0,0 +1,42 @@
+Async examples
+==============
+
+The Python language provides keywords for asynchronous operations, i.e.,
+"async" to define coroutines or "await" to schedule asynchronous calls in the
+event loop (see `PEP 492 <https://peps.python.org/pep-0492/>`_). It is up to
+packages to implement an event loop, support for these keywords, and more.
+
+One such package is `trio`. Since both an async package and Qt itself work with
+event loops, special care must be taken to ensure that both event loops work
+with each other. trio offers a dedicated `low-level API
+<https://trio.readthedocs.io/en/stable/reference-lowlevel.html>`_ for more
+complicated use cases such as this. Specifically, there exists a function
+`start_guest_run` that enables running the Trio event loop as a "guest" inside
+another event loop - Qt's in our case.
+
+Based on this functionality, two examples for async usage with Qt have been
+implemented: `eratosthenes` and `minimal`:
+
+.. image:: eratosthenes.svg
+ :alt: Async example: Eratosthenes
+ :width: 400
+
+* `eratosthenes` is a more extensive example that visualizes the Sieve of
+Eratosthenes algorithm. This algorithm per se is not one that is particularly
+suitable for asynchronous operations as it's not I/O-heavy, but synchronizing
+coroutines to a configurable tick allows for a good visualization.
+* `minimal` is a minimal example featuring a button that triggers an
+asynchronous coroutine with a sleep. It is designed to highlight which
+boilerplate code is essential for an async program with Qt and offers a
+starting point for more complex programs.
+
+Both examples feature:
+
+1. A window class.
+2. An `AsyncHelper` class containing `start_guest_run` plus helpers and
+callbacks necessary for its invocation. The entry point for the Trio guest run
+is provided as an argument from outside, which can be any async function.
+
+While `eratosthenes` offloads the asynchronous logic that will run in trio's
+event loop into a separate class, `minimal` demonstrates that async functions
+can be integrated into any class, including subclasses of Qt classes.