Thanks to visit codestin.com
Credit goes to github.com

Skip to content

make BlockingKernelClient the default Client #3222

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.

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 2 commits into from
Apr 27, 2013

Conversation

minrk
Copy link
Member

@minrk minrk commented Apr 27, 2013

The default Client class returned by KernelManager.client() should be BlockingKernelClient, because the base KernelClient is incomplete.

Ultimately, the base KernelClient will probably become a blocking client, and the Blocking subclass will go away.

minrk added 2 commits April 26, 2013 17:02
the default Client class returned by `KernelManager.client()`
should be BlockingKernelClient, because the base KernelClient is incomplete.

Ultimately, the base KernelClient will probably become a blocking client,
and the Blocking subclass will go away.
@ellisonbg
Copy link
Member

The kernel client used by the notebook is still the zmq based event loop one right?

@minrk
Copy link
Member Author

minrk commented Apr 27, 2013

Yes, the only effect this has is making the base KernelManager.client method usable, which it is not currently in master, since the base KernelClient is an incomplete base class.

ellisonbg added a commit that referenced this pull request Apr 27, 2013
make BlockingKernelClient the default Client
@ellisonbg ellisonbg merged commit 9cd4956 into ipython:master Apr 27, 2013
@minrk minrk deleted the blockingdefault branch March 31, 2014 23:36
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this pull request Nov 3, 2014
make BlockingKernelClient the default Client
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants