-
Notifications
You must be signed in to change notification settings - Fork 135
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
Conversation
c4c91dd
to
98dd21b
Compare
kernel_gateway/gatewayapp.py
Outdated
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 |
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.
We shouldn't have API warnings from Jupyter Client in the kernel gateway code, I think.
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.
I wasn't sure what the format for help would be so I copied it from Jupyter Notebook
@rolweber I've updated the PR with the suggested changes. Please review it. |
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. |
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.
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
resolves #265