Skip to content
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

AttributeError: 'BlockingKernelClient' object has no attribute 'started_channels' #3668

Closed
mspacek opened this issue Jul 17, 2013 · 3 comments · Fixed by #3669
Closed

AttributeError: 'BlockingKernelClient' object has no attribute 'started_channels' #3668

mspacek opened this issue Jul 17, 2013 · 3 comments · Fixed by #3669
Milestone

Comments

@mspacek
Copy link
Contributor

mspacek commented Jul 17, 2013

I have an app that is centered around IPython running in qt (https://github.com/neuropy/neuropy/blob/master/neuropy/main.py). Yesterday I updated IPython from git, and have had to change a few things since the refactoring about 3 months ago, which split a kernel client off of the kernel manager (see #3011). In the process, I came across the error in the title. This error only happens when I try to create a normal two-process app, but not when creating an inprocess app, ie, it happens with QtKernelManager, but not with QtInProcessKernelManager. I think a BlockingKernelClient happens to be the default for QtKernelClient, which may be due to #3222. Not sure how to fix this in IPython, but to get around it, I set the client_factory to QtKernelClient, and then calling QtKernelManager.client() works fine. My minimalist example is in this gist: https://gist.github.com/mspacek/6018206

Can this be fixed so that setting up the 2-process app doesn't require the extra step of changing the client_factory?

@ivanov
Copy link
Member

ivanov commented Jul 17, 2013

pinging @minrk who did the refactor

@minrk
Copy link
Member

minrk commented Jul 17, 2013

yup, left out a line. See #3669.

minrk added a commit that referenced this issue Jul 17, 2013
set default client_class for QtKernelManager

closes #3668
@mspacek
Copy link
Contributor Author

mspacek commented Jul 17, 2013

Thanks! I've updated the gist (https://gist.github.com/mspacek/6018206) to match. It's all very symmetric now for the two types of Qt kernels.

mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
set default client_class for QtKernelManager

closes ipython#3668
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants