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

Deprecate ipyparallel-specific code #71

Merged
merged 5 commits into from
Feb 8, 2016

Conversation

minrk
Copy link
Member

@minrk minrk commented Oct 29, 2015

  • deprecation warnings on serialization, data pub
  • Move ipyparallel-specific metadata to methods easier to override in subclasses
  • deprecate handling messages not in spec: apply, clear, abort.

related: ipython/ipyparallel#61

closes #17

minrk added 2 commits October 29, 2015 11:51
Will allow ipyparallel subclassing to be cleaner
@minrk minrk added this to the 4.2 milestone Oct 29, 2015
delay instantiation in order to show deprecation message
@minrk
Copy link
Member Author

minrk commented Nov 12, 2015

This should be ready to go. I'll merge in the next day or so unless I hear otherwise.

@minrk minrk changed the title Deprecate ipyparallel-specific code: Deprecate ipyparallel-specific code Nov 25, 2015
@minrk minrk modified the milestones: 4.3, 4.2 Nov 25, 2015
@minrk
Copy link
Member Author

minrk commented Nov 25, 2015

I changed my mind a little - I'll wait until we can ship ipyparallel 5.0 before releasing this one. Should be soon.

@minrk
Copy link
Member Author

minrk commented Feb 5, 2016

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
Copy link
Member

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?

Copy link
Member Author

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.

@takluyver
Copy link
Member

Other than those things, 👍

add should_handle short-circuit method for implementing abort
@minrk minrk force-pushed the deprecate-parallel branch from 7d771e0 to 3e94318 Compare February 7, 2016 11:46
@minrk
Copy link
Member Author

minrk commented Feb 7, 2016

Comments/docstrings updated to address the comments.

@minrk minrk force-pushed the deprecate-parallel branch from 3e94318 to 07da04e Compare February 8, 2016 07:53
takluyver added a commit that referenced this pull request Feb 8, 2016
Deprecate ipyparallel-specific code
@takluyver takluyver merged commit 3cf2ab5 into ipython:master Feb 8, 2016
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.

Proposal: remove some ipyparallel-specific functionality
2 participants