We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent cf30ce7 commit 0d8654fCopy full SHA for 0d8654f
doc/users/explain/interactive_guide.rst
@@ -166,8 +166,8 @@ takes over again.
166
This time-share technique only allows the event loop to run while
167
python is otherwise idle and waiting for user input. If you want the
168
GUI to be responsive during long running code it is necessary to
169
-periodically flush the GUI event queue as described :ref:`above
170
-<spin_event_loop>`. In this case it is your code, not the REPL, which
+periodically flush the GUI event queue as described :ref:`spin_event_loop`.
+In this case it is your code, not the REPL, which
171
is blocking the process so you need to handle the "time-share" manually.
172
Conversely, a very slow figure draw will block the prompt until it
173
finishes drawing.
0 commit comments