Install Kernel Specifications into userspace
This code installs jupyter kernels for different languages into the user space. Once the kernel has been installed it can be used on the jupyter-hub server of DKRZ.
Installation
python3 -m pip install jupyter-kernel-install
Usage
Using the command line interface (cli):
jupyter-kernel-install --help
Usage: jupyter-kernel-install [-h] [--name NAME] [--display-name DISPLAY_NAME] [--version] language
Install jupyter kernel specs of different languages.
Positional Arguments:
language The programming language
Options:
-h, --help show this help message and exit
--name, -n NAME The name of the kernel (default: None)
--display-name, -d DISPLAY_NAME
The display name of the kernel (default: None)
--version, -V Display version and exit
Alternatively you can use:
python -m jupyter_kernel_install --help
The following kernel specifications are supported:
- python3
- gnuR
- bash
Example for installing a gnuR kernel:
jupyter-kernel-install r --name r-regiklim --display-name "R for Regiklim"
Using the python library
Example for programmatically installing a bash kernel:
import jupyter_kernel_install as ki
kernel_path = ki.bash(name="bash-regiklim", display_name="bash kernel")
Contributing
Any contributions are welcome. To start developing we recommend creating a new mini conda environment.
conda env create -f environment.yml; conda activate install-kernelspec
Unit tests, building the documentation, type annotations and code style tests are done with tox. To run all tests, linting in parallel simply execute the following command:
tox -p 3
You can also run the each part alone, for example to only check the code style:
tox -e lint
available options are lint, types and test.
Tox runs in a separate python environment to run the tests in the current environment use:
pytest
Metadata
Release files for jupyter-kernel-install 2407.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_install-2407.0.1.tar.gz | 11.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyter_kernel_install-2407.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.4 kB
Release files / jupyter_kernel_install-2407.0.1.tar.gz
| Download URL | jupyter_kernel_install-2407.0.1.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b9760b08d008d513a698e7670a3a0ba3c1dee33ddbe4a2c9073dc586cdfd15c
|
|
BLAKE2b-256 checksum How to use checksums |
6537df998c835f8822dbee6e8b670a071aca6e9ddcc55a73d36cba5946bd6d51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Release files / jupyter_kernel_install-2407.0.1-py3-none-any.whl
| Download URL | jupyter_kernel_install-2407.0.1-py3-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5e43229be62c06d56c73fa5f126d3e6f534d91616971a80607fa1c11e31d2965
|
|
BLAKE2b-256 checksum How to use checksums |
0795088dafe932147e0bcc2c7e407d03697b2eac7bba1959931728eb7dabaf02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Security for jupyter-kernel-install 2407.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.