Jupyter Kernel Proxy
This Jupyter kernel serves as a proxy to any already running kernel. It is meant to allow Jupyter Notebook to use kernels it cannot start itself, such as kernel embedded in another applications.
Jupyter Kernel Proxy was initially created as a way to use Jupyter Notebook using IPyIDA, but should work with any other embedded or remote kernel.
Install
Jupyter Kernel Proxy is on PyPi and can be installed using
pip install jupyter-kernel-proxy
The kernelspec must also be installed using:
python -m jupyter_kernel_proxy install
Usage
In Jupyter Notebook, start a new notebook and choose "Existing session" as kernel type.
When launched, the kernel proxy will try to connect to the last started kernel.
This is similar to what jupyter console --existing would do.
The kernel implements a magic %proxy command to allow connecting to other
running kernels. Only two subcommands are implemented: list and connect.
Here is an example usage:
In [ ]: %proxy list
kernel-382cad4b-2286-4ea0-bcb7-fcc30039ac78.json (proxy)
* kernel-55159.json (no name)
kernel-55151d00-21e4-4ea9-8dfd-b0842e27cba1.json (no name)
kernel-50889.json (no name)
In [1]: a = 5
In [ ]: %proxy connect 55151d00-21e4-4ea9-8dfd-b0842e27cba1
Connecting to kernel-55151d00-21e4-4ea9-8dfd-b0842e27cba1.json
In [1]: a = 4
In [2]: a
Out [2]: 4
In [ ]: %proxy connect kernel-55159.json
Connecting to kernel-55159.json
In [2]: a
Out [2]: 5
Metadata
Release files for jupyter-kernel-proxy 1.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 | |
|---|---|---|---|---|
| jupyter-kernel-proxy-1.0.1.tar.gz | 7.6 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyter_kernel_proxy-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
| jupyter_kernel_proxy-1.0.1-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 23.3 kB
Release files / jupyter-kernel-proxy-1.0.1.tar.gz
| Download URL | jupyter-kernel-proxy-1.0.1.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
766d70c2f4f2069b794941f452e6dc5b2f884d9c10107ee655ac539699096ef6
|
|
BLAKE2b-256 checksum How to use checksums |
5c0ab1d9093fd1fb16ac6575731006fe3766c51bd6a0752cf6b36c826dab370a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Release files / jupyter_kernel_proxy-1.0.1-py3-none-any.whl
| Download URL | jupyter_kernel_proxy-1.0.1-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
37e66bbca623a4be932647934cd4efeb1ce2b76d3192db2dab1620d586c31244
|
|
BLAKE2b-256 checksum How to use checksums |
ab188da1b26713c8ae0fe63c665fcd192af3671d6f7a48288a649424d2f94f63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Release files / jupyter_kernel_proxy-1.0.1-py2-none-any.whl
| Download URL | jupyter_kernel_proxy-1.0.1-py2-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
ce7c4e9d97f88b1242dc4f71c912d1e4513982bfa0dc1852a9f335b2aba654ba
|
|
BLAKE2b-256 checksum How to use checksums |
133a257a49807f99d1116be4fb19805892ae66cd3287b249842208225ee11317
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Security for jupyter-kernel-proxy 1.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.