Skip to content

Additional run-time configurations for Kernel Gateway #266

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 1 commit into from
Nov 11, 2017

Conversation

shiti-saxena
Copy link
Contributor

resolves #265

@shiti-saxena shiti-saxena force-pushed the master branch 2 times, most recently from c4c91dd to 98dd21b Compare November 1, 2017 03:01
The kernel spec manager class to use. Should be a subclass
of `jupyter_client.kernelspec.KernelSpecManager`.

The Api of KernelSpecManager is provisional and might change
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't have API warnings from Jupyter Client in the kernel gateway code, I think.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't sure what the format for help would be so I copied it from Jupyter Notebook

@shiti-saxena
Copy link
Contributor Author

@rolweber I've updated the PR with the suggested changes. Please review it.

@parente
Copy link
Contributor

parente commented Nov 11, 2017

The config options look reasonable to me for advanced users. Anyone looking to add a custom kernel manager will need to be careful to support all the mode and option behaviors of the default managers.

@parente parente merged commit 99492c1 into jupyter-server:master Nov 11, 2017
kevin-bates added a commit to kevin-bates/enterprise_gateway that referenced this pull request Nov 27, 2017
Applied the recent [JKG PR 266](jupyter-server/kernel_gateway#266)
that allows for overrides to the kernelspec and kernel manager
classes.  Since Enterprise Gateway requires the remote kernel manager
classes already, they have been applied as the default values.

Users of this feature relative to JKG should still be able to retain
their current functionality. However, because those classes won't
derive from EG's remote kernel manager classes, they will not be able to
leverage the remoting features of EG until those classes also derive
from EG's remote kernel manager classes.
lresende pushed a commit to jupyter-server/enterprise_gateway that referenced this pull request Dec 1, 2017
Applied the recent PR jupyter-server/kernel_gateway#266
that allows for overrides to the kernelspec and kernel manager
classes.  Since Enterprise Gateway requires the remote kernel manager
classes already, they have been applied as the default values.

Users of this feature relative to JKG should still be able to retain
their current functionality. However, because those classes won't
derive from EG's remote kernel manager classes, they will not be able to
leverage the remoting features of EG until those classes also derive
from EG's remote kernel manager classes.

Closes #233
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.

Make KernelSpecManager and KernelManager configurable
3 participants