%global _empty_manifest_terminate_build 0
Name:		python-bavard
Version:	0.0.57
Release:	1
Summary:	A library and CLI for NLP and chatbot tasks
License:	MIT License
URL:		https://github.com/bavard-ai/bavard-nlu
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/c8/e3/34c76eeb9c4d46422d77d8dec7f804d259588f75b19bdd56c4b70df7f919/bavard-0.0.57.tar.gz
BuildArch:	noarch

Requires:	python3-bavard-ml-common
Requires:	python3-fire
Requires:	python3-keras-tuner
Requires:	python3-loguru
Requires:	python3-numpy
Requires:	python3-pydantic
Requires:	python3-scikit-learn
Requires:	python3-sentencepiece
Requires:	python3-spacy
Requires:	python3-tensorflow-probability
Requires:	python3-tensorflow
Requires:	python3-transformers
Requires:	python3-uncertainty-metrics
Requires:	python3-uvicorn

%description
# bavard-nlu

## Local Development

### Install Dependencies

```
pip3 install -e .
pip3 install -r requirements-test.txt
```

### Testing Locally

The tests for this repo consist of functional tests for catching bugs/code regressions, validation tests for catching model performance regressions, and integration tests for testing the NLU docker containers and their interactions. The validation and integration tests take much longer to execute. All are run in CI. To run the tests locally:

```
./test/scripts/lint-and-test.sh <test_suite>
```

Where `<test_suite` denotes the type of tests to run, and allows these options:
- `functional` - Runs just the functional tests.
- `integration` (default) - Runs both the functional and integration tests.
- `all` - Runs the functional, integration, and validation tests.

To run both the functional and integration tests:

### The Package CLI

There is a convenience CLI for training, evaluating, predicting, tuning, and interacting with NLU and dialogue policy models. To see the CLI documentation:

```
python3 -m bavard --help
```

You can also view the documentation for a sub-command for example:

```
python3 -m bavard nlu evaluate  --help
```

## Releasing The Package

Releasing the package is automatically handled by CI, but three steps must be taken to trigger a successful release:

1. Increment the `VERSION` variable in `setup.py` to the new desired version (e.g. `VERSION="1.1.1"`)
2. Commit and tag the repo with the **exact same** value you populated the `VERSION` variable with (e.g. `git tag 1.1.1`)
3. Push the commit and tag to remote. These can be done together using: `git push --atomic origin <branch name> <tag>`

CI will then release the package to pypi with that version once the commit and tag are pushed.




%package -n python3-bavard
Summary:	A library and CLI for NLP and chatbot tasks
Provides:	python-bavard
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-bavard
# bavard-nlu

## Local Development

### Install Dependencies

```
pip3 install -e .
pip3 install -r requirements-test.txt
```

### Testing Locally

The tests for this repo consist of functional tests for catching bugs/code regressions, validation tests for catching model performance regressions, and integration tests for testing the NLU docker containers and their interactions. The validation and integration tests take much longer to execute. All are run in CI. To run the tests locally:

```
./test/scripts/lint-and-test.sh <test_suite>
```

Where `<test_suite` denotes the type of tests to run, and allows these options:
- `functional` - Runs just the functional tests.
- `integration` (default) - Runs both the functional and integration tests.
- `all` - Runs the functional, integration, and validation tests.

To run both the functional and integration tests:

### The Package CLI

There is a convenience CLI for training, evaluating, predicting, tuning, and interacting with NLU and dialogue policy models. To see the CLI documentation:

```
python3 -m bavard --help
```

You can also view the documentation for a sub-command for example:

```
python3 -m bavard nlu evaluate  --help
```

## Releasing The Package

Releasing the package is automatically handled by CI, but three steps must be taken to trigger a successful release:

1. Increment the `VERSION` variable in `setup.py` to the new desired version (e.g. `VERSION="1.1.1"`)
2. Commit and tag the repo with the **exact same** value you populated the `VERSION` variable with (e.g. `git tag 1.1.1`)
3. Push the commit and tag to remote. These can be done together using: `git push --atomic origin <branch name> <tag>`

CI will then release the package to pypi with that version once the commit and tag are pushed.




%package help
Summary:	Development documents and examples for bavard
Provides:	python3-bavard-doc
%description help
# bavard-nlu

## Local Development

### Install Dependencies

```
pip3 install -e .
pip3 install -r requirements-test.txt
```

### Testing Locally

The tests for this repo consist of functional tests for catching bugs/code regressions, validation tests for catching model performance regressions, and integration tests for testing the NLU docker containers and their interactions. The validation and integration tests take much longer to execute. All are run in CI. To run the tests locally:

```
./test/scripts/lint-and-test.sh <test_suite>
```

Where `<test_suite` denotes the type of tests to run, and allows these options:
- `functional` - Runs just the functional tests.
- `integration` (default) - Runs both the functional and integration tests.
- `all` - Runs the functional, integration, and validation tests.

To run both the functional and integration tests:

### The Package CLI

There is a convenience CLI for training, evaluating, predicting, tuning, and interacting with NLU and dialogue policy models. To see the CLI documentation:

```
python3 -m bavard --help
```

You can also view the documentation for a sub-command for example:

```
python3 -m bavard nlu evaluate  --help
```

## Releasing The Package

Releasing the package is automatically handled by CI, but three steps must be taken to trigger a successful release:

1. Increment the `VERSION` variable in `setup.py` to the new desired version (e.g. `VERSION="1.1.1"`)
2. Commit and tag the repo with the **exact same** value you populated the `VERSION` variable with (e.g. `git tag 1.1.1`)
3. Push the commit and tag to remote. These can be done together using: `git push --atomic origin <branch name> <tag>`

CI will then release the package to pypi with that version once the commit and tag are pushed.




%prep
%autosetup -n bavard-0.0.57

%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-bavard -f filelist.lst
%dir %{python3_sitelib}/*

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

%changelog
* Tue May 30 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.57-1
- Package Spec generated