Skip to content

Backport PR #24645 on branch v3.6.2-doc (Removed 'above' wording from Input hook integration docs (#24632)) #24651

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 7, 2022
+2 −2
Merged

Backport PR #24645 on branch v3.6.2-doc (Removed 'above' wording from Input hook integration docs (#24632)) #24651

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/users/explain/interactive_guide.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,8 +166,8 @@ takes over again.
This time-share technique only allows the event loop to run while
python is otherwise idle and waiting for user input. If you want the
GUI to be responsive during long running code it is necessary to
periodically flush the GUI event queue as described :ref:`above
<spin_event_loop>`. In this case it is your code, not the REPL, which
periodically flush the GUI event queue as described in :ref:`spin_event_loop`.
In this case it is your code, not the REPL, which
is blocking the process so you need to handle the "time-share" manually.
Conversely, a very slow figure draw will block the prompt until it
finishes drawing.
Expand Down