pyviz_comms
Offers a simple bidirectional communication architecture between Python and JavaScript, with support for Jupyter comms in both the classic notebook and Jupyterlab. Available for use by any PyViz tool, but currently primarily used by HoloViz tools.
There are two installable components in this repository: a Python component used by various HoloViz tools and an extension to enable Jupyterlab support.
Installing the Jupyterlab extension
Jupyterlab users will need to install the Jupyterlab pyviz extension:
jupyter labextension install @pyviz/jupyterlab_pyviz
Compatibility
The Holoviz libraries are generally version independent of
JupyterLab and the jupyterlab_pyviz extension
has been supported since holoviews 1.10.0 and the first release of pyviz_comms.
Our goal is that jupyterlab_pyviz minor releases (using the SemVer pattern) are
made to follow JupyterLab minor release bumps and micro releases are for new jupyterlab_pyviz features
or bug fix releases. We've been previously inconsistent with having the extension release minor version bumps
track that of JupyterLab, so users seeking to find extension releases that are compatible with their JupyterLab
installation may refer to the below table.
Compatible JupyterLab and jupyterlab_pyviz versions
| JupyterLab | jupyterlab_pyviz |
|---|---|
| 0.33.x | 0.6.0 |
| 0.34.x | 0.6.1-0.6.2 |
| 0.35.x | 0.6.3-0.7.2 |
| 1.0.x | 0.8.0 |
| 2.0.x | 0.9.0-1.0.3 |
Developing the Jupyterlab extension
For a development install (requires npm version 4 or later), do the following in the repository directory:
npm install
jupyter labextension link .
To rebuild the package and the JupyterLab app:
npm run build
jupyter lab build
The pyviz_comms Python package
The pyviz_comms Python package is used by holoviz projects and can be
pip and conda installed.
Metadata
Release files for pyviz-comms 0.7.5
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 |
|---|---|---|---|---|
| pyviz_comms-0.7.5.tar.gz | 11.1 kB | Without provenance | Details for pyviz_comms-0.7.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyviz_comms-0.7.5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for pyviz_comms-0.7.5-py2.py3-none-any.whl |
Total release size: 21.7 kB
Release files / pyviz_comms-0.7.5.tar.gz
| Download URL | pyviz_comms-0.7.5.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
daa758ec7d7b519b0e315757cdedbf4b385600a5bcbb71af66100804b98423c9
|
|
BLAKE2b-256 checksum How to use checksums |
42d2496e8b179fc4aa2649f3ea52c469595a1801a8745d2bea2f46c4ff38d002
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1.post20200604 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.6
|
Release files / pyviz_comms-0.7.5-py2.py3-none-any.whl
| Download URL | pyviz_comms-0.7.5-py2.py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
d0f0c772b00d7d94cdd9734e128f65d984552c11181c0ad478fabd6e10530152
|
|
BLAKE2b-256 checksum How to use checksums |
291aecb1f6692d2ac99b3fd778908914fe1eee79c048d83654fbb04027a9606e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1.post20200604 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.6
|
Security for pyviz-comms 0.7.5
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.