Skip to content

Commit 49aabf9

Browse files
committed
Clarify the implied required busy/idle messages.
These messages were actually required, but you had to read the status message documentation to realize they were required. This makes the requirement more explicit.
1 parent b680593 commit 49aabf9

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/messaging.rst

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -147,8 +147,9 @@ Compatibility
147147
=============
148148

149149
Kernels must implement the :ref:`execute <execute>` and :ref:`kernel info
150-
<msging_kernel_info>` messages in order to be usable. All other message types
151-
are optional, although we recommend implementing :ref:`completion
150+
<msging_kernel_info>` messages, along with the associated busy and idle
151+
:ref:`status` messages. All other message types are
152+
optional, although we recommend implementing :ref:`completion
152153
<msging_completion>` if possible. Kernels do not need to send any reply for
153154
messages they don't handle, and frontends should provide sensible behaviour if
154155
no reply arrives (except for the required execution and kernel info messages).

0 commit comments

Comments
 (0)