async-kernel 0.13.0__tar.gz → 0.13.2__tar.gz

{async_kernel-0.13.0 → async_kernel-0.13.2}/.github/workflows/publish-to-pypi.yml

@@ -39,7 +39,7 @@ jobs:
       - name: Build a binary wheel and a source tarball
         run: uv build
       - name: Store the distribution packages
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         with:
           name: python-package-distributions
           path: dist/
@@ -61,7 +61,7 @@ jobs:
 
     steps:
       - name: Download all the dists
-        uses: actions/download-artifact@v7
+        uses: actions/download-artifact@v8
         with:
           name: python-package-distributions
           path: dist/
@@ -84,7 +84,7 @@ jobs:
 
     steps:
       - name: Download all the dists
-        uses: actions/download-artifact@v7
+        uses: actions/download-artifact@v8
         with:
           name: python-package-distributions
           path: dist/
@@ -112,7 +112,7 @@ jobs:
           fetch-depth: 0
           ref: main
       - name: Download all the dists
-        uses: actions/download-artifact@v7
+        uses: actions/download-artifact@v8
         with:
           name: python-package-distributions
           path: dist/

{async_kernel-0.13.0 → async_kernel-0.13.2}/.pre-commit-config.yaml

@@ -28,7 +28,7 @@ repos:
       - id: check-json5
 
   - repo: https://github.com/python-jsonschema/check-jsonschema
-    rev: 0.36.2
+    rev: 0.37.0
     hooks:
       - id: check-github-workflows
 
@@ -48,7 +48,7 @@ repos:
         additional_dependencies: [black==23.7.0]
 
   - repo: https://github.com/codespell-project/codespell
-    rev: v2.4.1
+    rev: v2.4.2
     hooks:
       - id: codespell
         args: ["-L", "sur,nd"]
@@ -59,7 +59,7 @@ repos:
       - id: python-use-type-annotations
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.15.2
+    rev: v0.15.6
     hooks:
       - id: ruff-check
         types_or: [python, jupyter]
@@ -68,7 +68,7 @@ repos:
         types_or: [python, jupyter]
 
   - repo: https://github.com/scientific-python/cookie
-    rev: 2025.11.21
+    rev: 2026.03.02
     hooks:
       - id: sp-repo-review
         additional_dependencies: ["repo-review[cli]"]

{async_kernel-0.13.0 → async_kernel-0.13.2}/CHANGELOG.md

@@ -5,6 +5,48 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.13.2] - 2026-03-15
+
+### <!-- 0 --> 🏗️ Breaking changes
+
+- Simplify message handling [#357](https://github.com/fleming79/async-kernel/pull/357)
+
+### <!-- 1 --> 🚀 Features
+
+- Add more methods defined on the IPyKernels base Kernel. [#354](https://github.com/fleming79/async-kernel/pull/354)
+
+### <!-- 5 --> 📝 Documentation
+
+- Update documentation [#356](https://github.com/fleming79/async-kernel/pull/356)
+
+### <!-- 6 --> 🌀 Miscellaneous
+
+- Prevent signal interrupt when the debugger is paused [#359](https://github.com/fleming79/async-kernel/pull/359)
+
+- Pre-commit and uv.lock update [#358](https://github.com/fleming79/async-kernel/pull/358)
+
+- Do not prevent message types on the shell channel. [#355](https://github.com/fleming79/async-kernel/pull/355)
+
+- Bump asyncio_guest to 71st revision. [#353](https://github.com/fleming79/async-kernel/pull/353)
+
+- Bump asyncio_guest to 69th rev (Better ProactorEventLoop experience) [#352](https://github.com/fleming79/async-kernel/pull/352)
+
+## [0.13.1] - 2026-03-02
+
+### <!-- 2 --> 🐛 Fixes
+
+- Fix Caller.as_complete not returning for empty iterable. [#349](https://github.com/fleming79/async-kernel/pull/349)
+
+### <!-- 5 --> 📝 Documentation
+
+- Tidy up asyncshell.py. [#350](https://github.com/fleming79/async-kernel/pull/350)
+
+### <!-- 6 --> 🌀 Miscellaneous
+
+- Prepare for release v0.13.1 [#351](https://github.com/fleming79/async-kernel/pull/351)
+
+- Bump the actions group with 2 updates [#348](https://github.com/fleming79/async-kernel/pull/348)
+
 ## [0.13.0] - 2026-03-01
 
 ### <!-- 1 --> 🚀 Features
@@ -19,6 +61,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### <!-- 6 --> 🌀 Miscellaneous
 
+- Prepare for release v0.13.0 [#347](https://github.com/fleming79/async-kernel/pull/347)
+
 - Change msg_type from "display_data" to "execute_result" in finish_displayhook. [#343](https://github.com/fleming79/async-kernel/pull/343)
 
 ## [0.12.5] - 2026-02-25
@@ -955,6 +999,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Bump the actions group across 1 directory with 2 updates [#3](https://github.com/fleming79/async-kernel/pull/3)
 
+[0.13.2]: https://github.com/fleming79/async-kernel/compare/v0.13.1..v0.13.2
+[0.13.1]: https://github.com/fleming79/async-kernel/compare/v0.13.0..v0.13.1
 [0.13.0]: https://github.com/fleming79/async-kernel/compare/v0.12.5..v0.13.0
 [0.12.5]: https://github.com/fleming79/async-kernel/compare/v0.12.4..v0.12.5
 [0.12.4]: https://github.com/fleming79/async-kernel/compare/v0.12.3..v0.12.4

{async_kernel-0.13.0 → async_kernel-0.13.2}/CONTRIBUTING.md

@@ -159,7 +159,7 @@ These links are not relevant for docstrings.
 - [footnotes](https://squidfunk.github.io/mkdocs-material/reference/footnotes/#usage)
 - [tooltips](https://squidfunk.github.io/mkdocs-material/reference/tooltips/#usage)
 
-## Releasing async kernel
+## Releasing async-kernel
 
 To make a new release go to the [new_release.yml](https://github.com/fleming79/async-kernel/actions/workflows/new_release.yml) action
 and click 'Run workflow'.

{async_kernel-0.13.0 → async_kernel-0.13.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: async-kernel
-Version: 0.13.0
+Version: 0.13.2
 Summary: A concurrent python kernel for Jupyter supporting AnyIO, AsyncIO and Trio.
 Project-URL: Homepage, https://fleming79.github.io/async-kernel
 Project-URL: Documentation, https://fleming79.github.io/async-kernel
@@ -47,7 +47,7 @@ Requires-Dist: typing-extensions>=4.14
 Requires-Dist: wrapt>=2.0.1
 Description-Content-Type: text/markdown
 
-# async kernel
+# async-kernel
 
 [![pypi](https://img.shields.io/pypi/pyversions/async-kernel.svg)](https://pypi.python.org/pypi/async-kernel)
 [![downloads](https://img.shields.io/pypi/dm/async-kernel?logo=pypi&color=3775A9)](https://pypistats.org/packages/async-kernel)
@@ -60,7 +60,7 @@ Description-Content-Type: text/markdown
 
 ![logo-svg](https://github.com/user-attachments/assets/6781ec08-94e9-4640-b8f9-bb07a08e9587)
 
-async kernel is a Python kernel for [Jupyter](https://docs.jupyter.org/en/latest/projects/kernels.html#kernels-programming-languages)
+async-kernel is a Python kernel for [Jupyter](https://docs.jupyter.org/en/latest/projects/kernels.html#kernels-programming-languages)
 that provides concurrent message handling via an asynchronous backend (asyncio or trio).
 
 The kernel provides two external interfaces:
@@ -75,11 +75,11 @@ The kernel provides two external interfaces:
 - [aiologic](https://aiologic.readthedocs.io/latest/) thread-safe synchronisation primitives
 - [Backend agnostic multi-thread / multi-event loop management](https://fleming79.github.io/async-kernel/latest/reference/caller/#async_kernel.caller.Caller)
 - Per-subshell user_ns
-- GUI event loops [^1][^2]
+- GUI event loops [^1]
     - [x] inline
     - [x] ipympl
-    - [x] tk host and asyncio[^3] or trio[^4] backend running as a guest
-    - [x] qt host and asyncio[^3] or trio[^4] backend running as a guest
+    - [x] tk host and asyncio[^2] or trio[^3] backend running as a guest
+    - [x] qt host and asyncio[^2] or trio[^3] backend running as a guest
 - [Experimental](https://github.com/fleming79/echo-kernel) support for
   [Jupyterlite](https://github.com/jupyterlite/jupyterlite) (try it online [here](https://fleming79.github.io/echo-kernel/) 👈)
 - [Debugger client](https://jupyterlab.readthedocs.io/en/latest/user/debugger.html#debugger)
@@ -90,29 +90,40 @@ The kernel provides two external interfaces:
     deliberate design choice to to ensure good performance and reliability.
 
 [^2]:
-    It is also possible to use a caller to run a gui event loop
-    in a separate thread (with a backend running as a guest) if the gui allows it
-    (qt will only run in the main thread). Also note that pyplot will only permit
-    one interactive gui library per process.
-
-[^3]:
     The asyncio implementation of `start_guest_run` was written by
     [the author of aiologic](https://github.com/x42005e1f/aiologic) and provided as a
     [gist](https://gist.github.com/x42005e1f/857dcc8b6865a11f1ffc7767bb602779).
 
-[^4]: trio's [start_guest_run](https://trio.readthedocs.io/en/stable/reference-lowlevel.html#trio.lowlevel.start_guest_run).
+[^3]: trio's [start_guest_run](https://trio.readthedocs.io/en/stable/reference-lowlevel.html#trio.lowlevel.start_guest_run).
 
-### Prevent asynchronous deadlocks
+### Avoid deadlocks
 
 The standard (synchronous) kernel implementation processes messages sequentially irrespective
-of the message type. The problem being that long running execute requests will make the kernel
-non-responsive. Another problem exists when an asynchronous execute request awaits a result that is delivered
+of the message type. The problem being that long running execute requests make the kernel non-responsive.
+
+Another problem exists when an asynchronous execute request awaits a result that is delivered
 via a kernel message - this will cause a deadlock because the message will be stuck in the queue behind
 the _blocking_ execute request[^5].
 
-async kernel handles messages according to the channel, message type and subshell id. So widget com message
+async-kernel handles messages according to the channel, message type and subshell id. So widget com message
 will get processed in a separate queue to an execute request. Further detail is given in the [concurrency notebook](https://fleming79.github.io/async-kernel/latest/notebooks/concurrency/), a Jupyterlite version is available [here](https://fleming79.github.io/echo-kernel/).
 
+#### Example
+
+Try the following using a standard kernel and then try it with async-kernel.
+
+```python
+# Make the shell thread busy
+import time
+
+time.sleep(1e6)
+```
+
+Try the following in another cell:
+
+- code completion (`tab`)
+- docstring (`shift tab`)
+
 [^5]:
     IPyKernel _solves_ this issue specifically for widgets by using the concept of
     'widget coms over subshells'. Widget messages arrive in a different thread which on
@@ -126,16 +137,16 @@ pip install async-kernel
 
 ## Kernel specs
 
-A kernel spec with the name 'async' is added when async kernel is installed.
+A kernel spec with the name 'async' is added when async-kernel is installed.
 
 Kernel specs can be added/removed via the command line.
 
 ### Backends
 
 The backend set on the interface is the asynchronous library the kernel uses for message handling.
-It is also the asynchronous library directly available when executing code in cells or via a console[^4].
+It is also the asynchronous library directly available when executing code in cells or via a console[^3].
 
-[^4]:
+[^3]:
     Irrespective of the configured backend, functions/coroutines can be executed using a specific backend
     with the method [`call_using_backend`](https://fleming79.github.io/async-kernel/latest/reference/caller/#async_kernel.caller.Caller.call_using_backend).
 
@@ -177,5 +188,5 @@ For further detail about kernel spec customisation see [command line and kernel
 
 ## Origin
 
-async kernel started as a [fork](https://github.com/ipython/ipykernel/commit/8322a7684b004ee95f07b2f86f61e28146a5996d)
-of [IPyKernel](https://github.com/ipython/ipykernel). Thank you to the original contributors of IPyKernel that made async kernel possible.
+async-kernel started as a [fork](https://github.com/ipython/ipykernel/commit/8322a7684b004ee95f07b2f86f61e28146a5996d)
+of [IPyKernel](https://github.com/ipython/ipykernel). Thank you to the original contributors of IPyKernel that made async-kernel possible.

{async_kernel-0.13.0 → async_kernel-0.13.2}/README.md

@@ -1,4 +1,4 @@
-# async kernel
+# async-kernel
 
 [![pypi](https://img.shields.io/pypi/pyversions/async-kernel.svg)](https://pypi.python.org/pypi/async-kernel)
 [![downloads](https://img.shields.io/pypi/dm/async-kernel?logo=pypi&color=3775A9)](https://pypistats.org/packages/async-kernel)
@@ -11,7 +11,7 @@
 
 ![logo-svg](https://github.com/user-attachments/assets/6781ec08-94e9-4640-b8f9-bb07a08e9587)
 
-async kernel is a Python kernel for [Jupyter](https://docs.jupyter.org/en/latest/projects/kernels.html#kernels-programming-languages)
+async-kernel is a Python kernel for [Jupyter](https://docs.jupyter.org/en/latest/projects/kernels.html#kernels-programming-languages)
 that provides concurrent message handling via an asynchronous backend (asyncio or trio).
 
 The kernel provides two external interfaces:
@@ -26,11 +26,11 @@ The kernel provides two external interfaces:
 - [aiologic](https://aiologic.readthedocs.io/latest/) thread-safe synchronisation primitives
 - [Backend agnostic multi-thread / multi-event loop management](https://fleming79.github.io/async-kernel/latest/reference/caller/#async_kernel.caller.Caller)
 - Per-subshell user_ns
-- GUI event loops [^1][^2]
+- GUI event loops [^1]
     - [x] inline
     - [x] ipympl
-    - [x] tk host and asyncio[^3] or trio[^4] backend running as a guest
-    - [x] qt host and asyncio[^3] or trio[^4] backend running as a guest
+    - [x] tk host and asyncio[^2] or trio[^3] backend running as a guest
+    - [x] qt host and asyncio[^2] or trio[^3] backend running as a guest
 - [Experimental](https://github.com/fleming79/echo-kernel) support for
   [Jupyterlite](https://github.com/jupyterlite/jupyterlite) (try it online [here](https://fleming79.github.io/echo-kernel/) 👈)
 - [Debugger client](https://jupyterlab.readthedocs.io/en/latest/user/debugger.html#debugger)
@@ -41,29 +41,40 @@ The kernel provides two external interfaces:
     deliberate design choice to to ensure good performance and reliability.
 
 [^2]:
-    It is also possible to use a caller to run a gui event loop
-    in a separate thread (with a backend running as a guest) if the gui allows it
-    (qt will only run in the main thread). Also note that pyplot will only permit
-    one interactive gui library per process.
-
-[^3]:
     The asyncio implementation of `start_guest_run` was written by
     [the author of aiologic](https://github.com/x42005e1f/aiologic) and provided as a
     [gist](https://gist.github.com/x42005e1f/857dcc8b6865a11f1ffc7767bb602779).
 
-[^4]: trio's [start_guest_run](https://trio.readthedocs.io/en/stable/reference-lowlevel.html#trio.lowlevel.start_guest_run).
+[^3]: trio's [start_guest_run](https://trio.readthedocs.io/en/stable/reference-lowlevel.html#trio.lowlevel.start_guest_run).
 
-### Prevent asynchronous deadlocks
+### Avoid deadlocks
 
 The standard (synchronous) kernel implementation processes messages sequentially irrespective
-of the message type. The problem being that long running execute requests will make the kernel
-non-responsive. Another problem exists when an asynchronous execute request awaits a result that is delivered
+of the message type. The problem being that long running execute requests make the kernel non-responsive.
+
+Another problem exists when an asynchronous execute request awaits a result that is delivered
 via a kernel message - this will cause a deadlock because the message will be stuck in the queue behind
 the _blocking_ execute request[^5].
 
-async kernel handles messages according to the channel, message type and subshell id. So widget com message
+async-kernel handles messages according to the channel, message type and subshell id. So widget com message
 will get processed in a separate queue to an execute request. Further detail is given in the [concurrency notebook](https://fleming79.github.io/async-kernel/latest/notebooks/concurrency/), a Jupyterlite version is available [here](https://fleming79.github.io/echo-kernel/).
 
+#### Example
+
+Try the following using a standard kernel and then try it with async-kernel.
+
+```python
+# Make the shell thread busy
+import time
+
+time.sleep(1e6)
+```
+
+Try the following in another cell:
+
+- code completion (`tab`)
+- docstring (`shift tab`)
+
 [^5]:
     IPyKernel _solves_ this issue specifically for widgets by using the concept of
     'widget coms over subshells'. Widget messages arrive in a different thread which on
@@ -77,16 +88,16 @@ pip install async-kernel
 
 ## Kernel specs
 
-A kernel spec with the name 'async' is added when async kernel is installed.
+A kernel spec with the name 'async' is added when async-kernel is installed.
 
 Kernel specs can be added/removed via the command line.
 
 ### Backends
 
 The backend set on the interface is the asynchronous library the kernel uses for message handling.
-It is also the asynchronous library directly available when executing code in cells or via a console[^4].
+It is also the asynchronous library directly available when executing code in cells or via a console[^3].
 
-[^4]:
+[^3]:
     Irrespective of the configured backend, functions/coroutines can be executed using a specific backend
     with the method [`call_using_backend`](https://fleming79.github.io/async-kernel/latest/reference/caller/#async_kernel.caller.Caller.call_using_backend).
 
@@ -128,5 +139,5 @@ For further detail about kernel spec customisation see [command line and kernel
 
 ## Origin
 
-async kernel started as a [fork](https://github.com/ipython/ipykernel/commit/8322a7684b004ee95f07b2f86f61e28146a5996d)
-of [IPyKernel](https://github.com/ipython/ipykernel). Thank you to the original contributors of IPyKernel that made async kernel possible.
+async-kernel started as a [fork](https://github.com/ipython/ipykernel/commit/8322a7684b004ee95f07b2f86f61e28146a5996d)
+of [IPyKernel](https://github.com/ipython/ipykernel). Thank you to the original contributors of IPyKernel that made async-kernel possible.

{async_kernel-0.13.0 → async_kernel-0.13.2}/_version.py

@@ -28,7 +28,7 @@ version_tuple: VERSION_TUPLE
 commit_id: COMMIT_ID
 __commit_id__: COMMIT_ID
 
-__version__ = version = '0.13.0'
-__version_tuple__ = version_tuple = (0, 13, 0)
+__version__ = version = '0.13.2'
+__version_tuple__ = version_tuple = (0, 13, 2)
 
 __commit_id__ = commit_id = None