##// END OF EJS Templates
updated explanation of 'pyin' messages
Paul Ivanov -
Show More
@@ -395,6 +395,8 b' the outcome. See :ref:`below <execution_results>` for the possible return'
395 codes and associated data.
395 codes and associated data.
396
396
397
397
398 .. _execution_counter:
399
398 Execution counter (old prompt number)
400 Execution counter (old prompt number)
399 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
401 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
400
402
@@ -403,7 +405,7 b' requests that are made with ``store_history=True``. This counter is used to pop'
403 the ``In[n]``, ``Out[n]`` and ``_n`` variables, so clients will likely want to
405 the ``In[n]``, ``Out[n]`` and ``_n`` variables, so clients will likely want to
404 display it in some form to the user, which will typically (but not necessarily)
406 display it in some form to the user, which will typically (but not necessarily)
405 be done in the prompts. The value of this counter will be returned as the
407 be done in the prompts. The value of this counter will be returned as the
406 ``execution_count`` field of all ``execute_reply`` messages.
408 ``execution_count`` field of all ``execute_reply`` and ``pyin`` messages.
407
409
408 .. _execution_results:
410 .. _execution_results:
409
411
@@ -906,7 +908,10 b' to update a single namespace with subsequent results.'
906 Python inputs
908 Python inputs
907 -------------
909 -------------
908
910
909 These messages are the re-broadcast of the ``execute_request``.
911 To let all frontends know what code is being executed at any given time, these
912 messages contain a re-broadcast of the ``code`` portion of an
913 :ref:`execute_request <execute>`, along with the :ref:`execution_count
914 <execution_counter>`.
910
915
911 Message type: ``pyin``::
916 Message type: ``pyin``::
912
917
General Comments 0
You need to be logged in to leave comments. Login now