upstream/ipython Files · IPython/core/tests/test_autocall.py

This feature was discussed in , but it doesn't look like anything was ever incorporated into the IPython Notebook....

This feature was discussed in , but it doesn't look like anything was ever incorporated into the IPython Notebook. Here's a brief overview of the changes: - Display of messages from other clients can be toggled on and off from within a notebook, either using the ``<M-m>e`` keyboard shortcut in the web UI, or through the option in the "Kernel" menu. - notebook.js controls whether messages are displayed through a callback that is invoked from kernel.js when no callbacks are available for a message. - The UI displays ``execute_input`` messages originating from an other clients in new cells at the end of the notebook. Output messages (``execute_result`` et al.) will only be displayed if a cell exists with a matching message ID. Pending design questions: - Should each ``execute_input`` message cause a new cell to be created? - Should new cells be placed at the end of the notebook, or elsewhere? If the latter, what criteria should be followed?

Thomas Kluyver - - Load All Authors

File last commit:

r4895:329e2362


                r19164:17ac8ca3

Download file

             test_autocall.py
        
                    45 lines
            
             | 971 B
            
                | text/x-python
            
             |
                PythonLexer
            
             / IPython / core / tests / test_autocall.py
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      """These kinds of tests are less than ideal, but at least they run.

      This was an old test that was being run interactively in the top-level tests/

      directory, which we are removing.  For now putting this here ensures at least

      we do run the test, though ultimately this functionality should all be tested

      with better-isolated tests that don't rely on the global instance in iptest.

      """

      from IPython.utils import py3compat

      @py3compat.doctest_refactor_print

      def doctest_autocall():

          """

          In [1]: def f1(a,b,c):

             ...:     return a+b+c

             ...: 

          In [2]: def f2(a):

             ...:     return a + a

             ...:   

          In [3]: ;f2 a b c

          Out[3]: 'a b ca b c'

          In [4]: assert _ == "a b ca b c"

          In [5]: ,f1 a b c

          Out[5]: 'abc'

          In [6]: assert _ == 'abc'

          In [7]: print _

          abc

          In [8]: /f1 1,2,3

          Out[8]: 6

          In [9]: assert _ == 6

          In [10]: /f2 4

          Out[10]: 8

          In [11]: assert _ == 8

          In [11]: del f1, f2

          """

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				"""These kinds of tests are less than ideal, but at least they run.

				This was an old test that was being run interactively in the top-level tests/
				directory, which we are removing. For now putting this here ensures at least
				we do run the test, though ultimately this functionality should all be tested
				with better-isolated tests that don't rely on the global instance in iptest.
				"""
				from IPython.utils import py3compat

				@py3compat.doctest_refactor_print
				def doctest_autocall():
				"""
				In [1]: def f1(a,b,c):
				...: return a+b+c
				...:

				In [2]: def f2(a):
				...: return a + a
				...:

				In [3]: ;f2 a b c
				Out[3]: 'a b ca b c'

				In [4]: assert _ == "a b ca b c"

				In [5]: ,f1 a b c
				Out[5]: 'abc'

				In [6]: assert _ == 'abc'

				In [7]: print _
				abc

				In [8]: /f1 1,2,3
				Out[8]: 6

				In [9]: assert _ == 6

				In [10]: /f2 4
				Out[10]: 8

				In [11]: assert _ == 8

				In [11]: del f1, f2
				"""