Show More
@@ -15,11 +15,16 b' To make IPython GUI event loop integration occur automatically at every' | |||
|
15 | 15 | startup, set the ``c.InteractiveShellApp.gui`` configuration key in your |
|
16 | 16 | IPython profile (see :ref:`setting_config`). |
|
17 | 17 | |
|
18 | Terminal IPython handles event loops very differently from the IPython kernel, | |
|
19 | so different steps are needed to integrate with each. | |
|
18 | If the event loop you use is supported by IPython, turning on event loop | |
|
19 | integration follows the steps just described whether you use Terminal IPython | |
|
20 | or an IPython kernel. | |
|
20 | 21 | |
|
21 | Event loops in the terminal | |
|
22 | --------------------------- | |
|
22 | However, the way Terminal IPython handles event loops is very different from | |
|
23 | the way IPython kernel does, so if you need to integrate with a new kind of | |
|
24 | event loop, different steps are needed to integrate with each. | |
|
25 | ||
|
26 | Integrating with a new event loop in the terminal | |
|
27 | ------------------------------------------------- | |
|
23 | 28 | |
|
24 | 29 | .. versionchanged:: 5.0 |
|
25 | 30 | |
@@ -56,8 +61,8 b' Once you have defined this function, register it with IPython:' | |||
|
56 | 61 | by running ``%gui foo``. |
|
57 | 62 | |
|
58 | 63 | |
|
59 |
|
|
|
60 | ------------------------- | |
|
64 | Integrating with a new event loop in the kernel | |
|
65 | ----------------------------------------------- | |
|
61 | 66 | |
|
62 | 67 | The kernel runs its own event loop, so it's simpler to integrate with others. |
|
63 | 68 | IPython allows the other event loop to take control, but it must call |
General Comments 0
You need to be logged in to leave comments.
Login now