path: root/python-pyviz-comms.spec

%global _empty_manifest_terminate_build 0
Name:		python-pyviz-comms
Version:	2.2.1
Release:	1
Summary:	Bidirectional communication for the HoloViz ecosystem.
License:	BSD
URL:		https://holoviz.org
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/1c/49/497af145fac6e8ec72d65b897b8e057093ec0cec3caa247ca6c34748429e/pyviz_comms-2.2.1.tar.gz
BuildArch:	noarch

Requires:	python3-param
Requires:	python3-flake8
Requires:	python3-jupyter-packaging
Requires:	python3-jupyterlab
Requires:	python3-keyring
Requires:	python3-pytest
Requires:	python3-rfc3986
Requires:	python3-setuptools
Requires:	python3-twine
Requires:	python3-setuptools
Requires:	python3-jupyterlab
Requires:	python3-jupyter-packaging
Requires:	python3-twine
Requires:	python3-rfc3986
Requires:	python3-keyring
Requires:	python3-flake8
Requires:	python3-pytest

%description
# pyviz_comms

![Github Actions Status](https://github.com/holoviz/pyviz_comms/workflows/test/badge.svg)

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](https://pyviz.org) tool, but currently primarily used by
[HoloViz](https://holoviz.org) tools.

There are two installable components in this repository: a Python
component used by various HoloViz tools and an extension to enable
Jupyterlab support. For JupyterLab 3.0 the extension is automatically
bundled with the `pyviz_comms` Python package.

## Installing the Jupyterlab extension

Jupyterlab users will need to install the Jupyterlab pyviz extension. Starting with JupyterLab 3.0 the extension will be automatically installed when installing `pyviz_comms` with `pip` using:

```bash
pip install pyviz_comms
```

or using `conda` with:

```bash
conda install -c pyviz pyviz_comms
```

For older versions of JupyterLab you must separately install:

```bash
jupyter labextension install @pyviz/jupyterlab_pyviz
```

## Compatibility

The [Holoviz](https://github.com/holoviz/holoviz) libraries are generally version independent of
[JupyterLab](https://github.com/jupyterlab/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](https://semver.org/) 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      |
| 3.x           | 2.0              |

## Developing the Jupyterlab extension

Note: You will need NodeJS to build the extension package.

The `jlpm` command is JupyterLab's pinned version of
[yarn](https://yarnpkg.com/) that is installed with JupyterLab. You may use
`yarn` or `npm` in lieu of `jlpm` below.

```bash
# Clone the repo to your local environment
# Change directory to the holoviz_jlab directory
# Install package in development mode
pip install -e .
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Rebuild extension Typescript source after making changes
jlpm run build
```

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

```bash
# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm run watch
# Run JupyterLab in another terminal
jupyter lab
```

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the `jlpm run build` command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

```bash
jupyter lab build --minimize=False
```




%package -n python3-pyviz-comms
Summary:	Bidirectional communication for the HoloViz ecosystem.
Provides:	python-pyviz-comms
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-pyviz-comms
# pyviz_comms

![Github Actions Status](https://github.com/holoviz/pyviz_comms/workflows/test/badge.svg)

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](https://pyviz.org) tool, but currently primarily used by
[HoloViz](https://holoviz.org) tools.

There are two installable components in this repository: a Python
component used by various HoloViz tools and an extension to enable
Jupyterlab support. For JupyterLab 3.0 the extension is automatically
bundled with the `pyviz_comms` Python package.

## Installing the Jupyterlab extension

Jupyterlab users will need to install the Jupyterlab pyviz extension. Starting with JupyterLab 3.0 the extension will be automatically installed when installing `pyviz_comms` with `pip` using:

```bash
pip install pyviz_comms
```

or using `conda` with:

```bash
conda install -c pyviz pyviz_comms
```

For older versions of JupyterLab you must separately install:

```bash
jupyter labextension install @pyviz/jupyterlab_pyviz
```

## Compatibility

The [Holoviz](https://github.com/holoviz/holoviz) libraries are generally version independent of
[JupyterLab](https://github.com/jupyterlab/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](https://semver.org/) 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      |
| 3.x           | 2.0              |

## Developing the Jupyterlab extension

Note: You will need NodeJS to build the extension package.

The `jlpm` command is JupyterLab's pinned version of
[yarn](https://yarnpkg.com/) that is installed with JupyterLab. You may use
`yarn` or `npm` in lieu of `jlpm` below.

```bash
# Clone the repo to your local environment
# Change directory to the holoviz_jlab directory
# Install package in development mode
pip install -e .
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Rebuild extension Typescript source after making changes
jlpm run build
```

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

```bash
# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm run watch
# Run JupyterLab in another terminal
jupyter lab
```

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the `jlpm run build` command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

```bash
jupyter lab build --minimize=False
```




%package help
Summary:	Development documents and examples for pyviz-comms
Provides:	python3-pyviz-comms-doc
%description help
# pyviz_comms

![Github Actions Status](https://github.com/holoviz/pyviz_comms/workflows/test/badge.svg)

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](https://pyviz.org) tool, but currently primarily used by
[HoloViz](https://holoviz.org) tools.

There are two installable components in this repository: a Python
component used by various HoloViz tools and an extension to enable
Jupyterlab support. For JupyterLab 3.0 the extension is automatically
bundled with the `pyviz_comms` Python package.

## Installing the Jupyterlab extension

Jupyterlab users will need to install the Jupyterlab pyviz extension. Starting with JupyterLab 3.0 the extension will be automatically installed when installing `pyviz_comms` with `pip` using:

```bash
pip install pyviz_comms
```

or using `conda` with:

```bash
conda install -c pyviz pyviz_comms
```

For older versions of JupyterLab you must separately install:

```bash
jupyter labextension install @pyviz/jupyterlab_pyviz
```

## Compatibility

The [Holoviz](https://github.com/holoviz/holoviz) libraries are generally version independent of
[JupyterLab](https://github.com/jupyterlab/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](https://semver.org/) 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      |
| 3.x           | 2.0              |

## Developing the Jupyterlab extension

Note: You will need NodeJS to build the extension package.

The `jlpm` command is JupyterLab's pinned version of
[yarn](https://yarnpkg.com/) that is installed with JupyterLab. You may use
`yarn` or `npm` in lieu of `jlpm` below.

```bash
# Clone the repo to your local environment
# Change directory to the holoviz_jlab directory
# Install package in development mode
pip install -e .
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Rebuild extension Typescript source after making changes
jlpm run build
```

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

```bash
# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm run watch
# Run JupyterLab in another terminal
jupyter lab
```

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the `jlpm run build` command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

```bash
jupyter lab build --minimize=False
```




%prep
%autosetup -n pyviz-comms-2.2.1

%build
%py3_build

%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .

%files -n python3-pyviz-comms -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Fri Apr 21 2023 Python_Bot <Python_Bot@openeuler.org> - 2.2.1-1
- Package Spec generated