Jupyter Kernel Gateway
Overview
Jupyter Kernel Gateway is a web server that provides headless access to Jupyter kernels. Your application communicates with the kernels remotely, through REST calls and Websockets rather than ZeroMQ messages. There are no provisions for editing notebooks through the Kernel Gateway. The following operation modes, called personalities, are supported out of the box:
-
Send code snippets for execution using the Jupyter kernel protocol over Websockets. Start and stop kernels through REST calls. This HTTP API is compatible with the respective API sections of the Jupyter Notebook server.
-
Serve HTTP requests from annotated notebook cells. The code snippets are cells of a static notebook configured in the Kernel Gateway. Annotations define which HTTP verbs and resources it supports. Incoming requests are served by executing one of the cells in a kernel.
Jupyter Kernel Gateway uses the same code as Jupyter Notebook to launch kernels in its local process/filesystem space. It can be containerized and scaled out using common technologies like tmpnb, Cloud Foundry, and Kubernetes.
Example Uses of Kernel Gateway
- Attach a local Jupyter Notebook server to a compute cluster in the cloud running near big data (e.g., interactive gateway to Spark)
- Enable a new breed of non-notebook web clients to provision and use kernels (e.g., web dashboards using jupyter-js-services)
- Create microservices from notebooks using the Kernel Gateway
notebook-httpmode
Features
See the Features page in the documentation for a list of the Jupyter Kernel Gateway features.
Installation
Detailed installation instructions are located in the
Getting Started page
of the project docs. Here's a quick start using pip:
# install from pypi
pip install jupyter_kernel_gateway
# show all config options
jupyter kernelgateway --help-all
# run it with default options
jupyter kernelgateway
Contributing
The Development page includes information about setting up a development environment and typical developer tasks.
Metadata
Release files for jupyter-kernel-gateway 3.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jupyter_kernel_gateway-3.0.1.tar.gz | 54.6 kB | Without provenance | Details for jupyter_kernel_gateway-3.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyter_kernel_gateway-3.0.1-py3-none-any.whl | Python 3 | none | any | Details for jupyter_kernel_gateway-3.0.1-py3-none-any.whl |
Total release size: 107.6 kB
Release files / jupyter_kernel_gateway-3.0.1.tar.gz
| Download URL | jupyter_kernel_gateway-3.0.1.tar.gz |
|---|---|
| Size | 54.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
900690c4c0e796867355468d685f7fa1cf3c7775d08e871c157f77d65fbd6d7f
|
|
BLAKE2b-256 checksum How to use checksums |
0ff46672cae9f6f36be7566496dbe2f78a8e39d4db73b36c2911c83320dd7027
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.11.8
|
Release files / jupyter_kernel_gateway-3.0.1-py3-none-any.whl
| Download URL | jupyter_kernel_gateway-3.0.1-py3-none-any.whl |
|---|---|
| Size | 53.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f74a2f4ff9f03737bcab79f44ae0f6473ee32deb30fce00b8f05adcdd023f03
|
|
BLAKE2b-256 checksum How to use checksums |
3da2e0a4616fde099b71ef996e5ae117451bc80b15f89807d1f3db9298644209
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.11.8
|
Security for jupyter-kernel-gateway 3.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.