Remove setting of the eventloop function in the InProcessKernel #781
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
enable_gui
function of the InProcessInteractiveShell calls a function of the same name in 'eventloops.py', which setskernel.eventloop
to a function defined by the requested GUI. For the InProcessKernel,kernel.eventloop
should always be set toNone
. Otherwise, commands typed in the shell trigger a call to the parent kernel class'senter_eventloop
function, which causes an exception because attributes likeio_loop
andmsg_queue
are not defined by the InProcessKernel.This PR removes the call to the
enable_gui
function in 'eventloops.py' since the Qt event loop should already be running in the InProcessKernel.This is designed to fix #780 and is possibly related to #775 and #319.