-
-
Notifications
You must be signed in to change notification settings - Fork 373
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
Deprecate ipyparallel-specific code #71
Conversation
it's moving to ipyparallel
Will allow ipyparallel subclassing to be cleaner
delay instantiation in order to show deprecation message
This should be ready to go. I'll merge in the next day or so unless I hear otherwise. |
I changed my mind a little - I'll wait until we can ship ipyparallel 5.0 before releasing this one. Should be soon. |
ipyparallel 5.0 shipped, so this should be able to go in, now. |
Run at the beginning of request handlers. | ||
""" | ||
md = super(IPythonKernel, self).init_metadata(parent) | ||
# FIXME: remove ipyparallel-specific code |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the plan for dealing with these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Going forward, these are provided by a subclass in ipyparallel. Removing these would be a breaking change, and would break ipyparallel < 5. We can consider dropping then in ipykernel 5 or 6.
Other than those things, 👍 |
add should_handle short-circuit method for implementing abort
7d771e0
to
3e94318
Compare
Comments/docstrings updated to address the comments. |
3e94318
to
07da04e
Compare
Deprecate ipyparallel-specific code
related: ipython/ipyparallel#61
closes #17