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

Fixed order of notebook loading and kernel starting....

Fixed order of notebook loading and kernel starting. For security reasons, the kernel should not be started until after the notebook content is completely loaded and on the page. This prevents people from creating notebooks that run nasty code on the users machine at load time. In order to implement this, we had to create a CodeCell.set_kernel method that allows the kernel attribute of a CodeCell to be set at a later time. This also fixes some error messages we were seeing related to the kernel's channels not being setup properly when a send was attempted.

Thomas Kluyver - - Load All Authors

File last commit:

r4895:329e2362


                r7197:ec9293e0

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
				"""