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

Backport PR : Let IPython.lib.guisupport detect terminal-integrated event loops...

Backport PR : Let IPython.lib.guisupport detect terminal-integrated event loops Closes gh-9974 This is a bit more invasive than most backported changes, but it fixes a regression in IPython 5. My thinking: - The `guisupport` APIs that worked before should continue working until/unless we deprecate them. - There should be a common way to check if an event loop is already running in both the terminal and an IPython kernel. - It should be possible to check for any event loop, not just Qt and Wx (which `guisupport` has checks for). My plan is to make a public attribute `shell.active_eventloop`, which is either None or a string naming the event loop which IPython will run when waiting for input. E.g. `qt` or `gtk3`. (Todo: should we also expose the event loop object in cases where there is one? Not sure if anything useful can be done with it). This PR adds that attribute for terminal IPython; if we agree on it I'll make a separate PR for ipykernel. The functions in guisupport then become a convenient shortcut for checking this, and we can decide whether to deprecate them in favour or something more uniform, or add similar convenience functions for other common event loops. Signed-off-by: Thomas Kluyver <thomas@kluyver.me.uk>

Thomas Kluyver - - Load All Authors

File last commit:

r4895:329e2362


                r23138:fb70b991

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