diff options
| author | CoprDistGit <infra@openeuler.org> | 2023-05-05 04:43:28 +0000 |
|---|---|---|
| committer | CoprDistGit <infra@openeuler.org> | 2023-05-05 04:43:28 +0000 |
| commit | f6ca3c0921cae36cddc4e8d4b4a62a72c94a882c (patch) | |
| tree | aa6cb78e92db8fad03534693cbc7ddc4c4b24e62 /python-cognite-extractor-utils.spec | |
| parent | f155ef70c2eaf02717018494edd8732af35e8d3e (diff) | |
automatic import of python-cognite-extractor-utilsopeneuler20.03
Diffstat (limited to 'python-cognite-extractor-utils.spec')
| -rw-r--r-- | python-cognite-extractor-utils.spec | 256 |
1 files changed, 256 insertions, 0 deletions
diff --git a/python-cognite-extractor-utils.spec b/python-cognite-extractor-utils.spec new file mode 100644 index 0000000..c595cae --- /dev/null +++ b/python-cognite-extractor-utils.spec @@ -0,0 +1,256 @@ +%global _empty_manifest_terminate_build 0 +Name: python-cognite-extractor-utils +Version: 4.3.1 +Release: 1 +Summary: Utilities for easier development of extractors for CDF +License: Apache-2.0 +URL: https://github.com/cognitedata/python-extractor-utils +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/32/1a/ae3efbd11fa88695494d95e3906d5d172cefb425391e0d6c6c33181c49d2/cognite_extractor_utils-4.3.1.tar.gz +BuildArch: noarch + +Requires: python3-arrow +Requires: python3-cognite-sdk +Requires: python3-cognite-sdk-experimental +Requires: python3-dacite +Requires: python3-decorator +Requires: python3-jq +Requires: python3-jq +Requires: python3-more-itertools +Requires: python3-prometheus-client +Requires: python3-psutil +Requires: python3-dotenv +Requires: python3-pyyaml +Requires: python3-typing-extensions + +%description +[](https://github.com/cognitedata/python-extractor-utils/actions) +[](https://cognite-extractor-utils.readthedocs-hosted.com/en/latest/?badge=latest) +[](https://codecov.io/gh/cognitedata/python-extractor-utils) +[](https://pypi.org/project/cognite-extractor-utils) + +[](LICENSE) +[](https://github.com/ambv/black) +The `extractor-utils` package is an extension of the Cognite Python SDK intended to simplify the development of data +extractors or other integrations for Cognite Data Fusion. +Documentation is hosted [here](https://cognite-extractor-utils.readthedocs-hosted.com/en/latest/), including a +[quickstart tutorial](https://cognite-extractor-utils.readthedocs-hosted.com/en/latest/quickstart.html). +The changelog is found [here](./CHANGELOG.md). +## Overview +The best way to start a new extractor project is to use the `cogex` CLI. You can install that from PyPI: +``` bash +pip install cognite-extractor-manager +``` +To initialize a new extractor project, run +``` bash +cogex init +``` +in the directory you want your extractor project in. The `cogex` CLI will prompt you for some information about your +project, and then set up a poetry environment, git repository, commit hooks with type and style checks and load a +template. +### Extensions +Some source systems have a lot in common, such as RESTful APIs or systems exposing as MQTT. We therefore have extensions +to `extractor-utils` tailroed to these protocols. These can be found in separate packages: + * [REST extension](https://github.com/cognitedata/python-extractor-utils-rest) + * [MQTT extension](https://github.com/cognitedata/python-extractor-utils-mqtt) +## Contributing +The package is open source under the [Apache 2.0 license](./LICENSE), and contribtuions are welcome. +This project adheres to the [Contributor Covenant v2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/) +as a code of conduct. +### Development environment +We use [poetry](https://python-poetry.org) to manage dependencies and to administrate virtual environments. To develop +`extractor-utils`, follow the following steps to set up your local environment: + 1. [Install poetry](https://python-poetry.org/docs/#installation) if you haven't already. + 2. Clone repository: + ``` + $ git clone git@github.com:cognitedata/python-extractor-utils.git + ``` + 3. Move into the newly created local repository: + ``` + $ cd python-extractor-utils + ``` + 4. Create virtual environment and install dependencies: + ``` + $ poetry install + ``` +### Code requirements +All code must pass [black](https://github.com/ambv/black) and [isort](https://github.com/timothycrosley/isort) style +checks to be merged. It is recommended to install pre-commit hooks to ensure this locally before commiting code: +``` +$ poetry run pre-commit install +``` +Each public method, class and module should have docstrings. Docstrings are written in the [Google +style](https://google.github.io/styleguide/pyguide.html#38-comments-and-docstrings). Please include unit and/or +integration tests for submitted code, and remember to update the [changelog](./CHANGELOG.md). + +%package -n python3-cognite-extractor-utils +Summary: Utilities for easier development of extractors for CDF +Provides: python-cognite-extractor-utils +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-cognite-extractor-utils +[](https://github.com/cognitedata/python-extractor-utils/actions) +[](https://cognite-extractor-utils.readthedocs-hosted.com/en/latest/?badge=latest) +[](https://codecov.io/gh/cognitedata/python-extractor-utils) +[](https://pypi.org/project/cognite-extractor-utils) + +[](LICENSE) +[](https://github.com/ambv/black) +The `extractor-utils` package is an extension of the Cognite Python SDK intended to simplify the development of data +extractors or other integrations for Cognite Data Fusion. +Documentation is hosted [here](https://cognite-extractor-utils.readthedocs-hosted.com/en/latest/), including a +[quickstart tutorial](https://cognite-extractor-utils.readthedocs-hosted.com/en/latest/quickstart.html). +The changelog is found [here](./CHANGELOG.md). +## Overview +The best way to start a new extractor project is to use the `cogex` CLI. You can install that from PyPI: +``` bash +pip install cognite-extractor-manager +``` +To initialize a new extractor project, run +``` bash +cogex init +``` +in the directory you want your extractor project in. The `cogex` CLI will prompt you for some information about your +project, and then set up a poetry environment, git repository, commit hooks with type and style checks and load a +template. +### Extensions +Some source systems have a lot in common, such as RESTful APIs or systems exposing as MQTT. We therefore have extensions +to `extractor-utils` tailroed to these protocols. These can be found in separate packages: + * [REST extension](https://github.com/cognitedata/python-extractor-utils-rest) + * [MQTT extension](https://github.com/cognitedata/python-extractor-utils-mqtt) +## Contributing +The package is open source under the [Apache 2.0 license](./LICENSE), and contribtuions are welcome. +This project adheres to the [Contributor Covenant v2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/) +as a code of conduct. +### Development environment +We use [poetry](https://python-poetry.org) to manage dependencies and to administrate virtual environments. To develop +`extractor-utils`, follow the following steps to set up your local environment: + 1. [Install poetry](https://python-poetry.org/docs/#installation) if you haven't already. + 2. Clone repository: + ``` + $ git clone git@github.com:cognitedata/python-extractor-utils.git + ``` + 3. Move into the newly created local repository: + ``` + $ cd python-extractor-utils + ``` + 4. Create virtual environment and install dependencies: + ``` + $ poetry install + ``` +### Code requirements +All code must pass [black](https://github.com/ambv/black) and [isort](https://github.com/timothycrosley/isort) style +checks to be merged. It is recommended to install pre-commit hooks to ensure this locally before commiting code: +``` +$ poetry run pre-commit install +``` +Each public method, class and module should have docstrings. Docstrings are written in the [Google +style](https://google.github.io/styleguide/pyguide.html#38-comments-and-docstrings). Please include unit and/or +integration tests for submitted code, and remember to update the [changelog](./CHANGELOG.md). + +%package help +Summary: Development documents and examples for cognite-extractor-utils +Provides: python3-cognite-extractor-utils-doc +%description help +[](https://github.com/cognitedata/python-extractor-utils/actions) +[](https://cognite-extractor-utils.readthedocs-hosted.com/en/latest/?badge=latest) +[](https://codecov.io/gh/cognitedata/python-extractor-utils) +[](https://pypi.org/project/cognite-extractor-utils) + +[](LICENSE) +[](https://github.com/ambv/black) +The `extractor-utils` package is an extension of the Cognite Python SDK intended to simplify the development of data +extractors or other integrations for Cognite Data Fusion. +Documentation is hosted [here](https://cognite-extractor-utils.readthedocs-hosted.com/en/latest/), including a +[quickstart tutorial](https://cognite-extractor-utils.readthedocs-hosted.com/en/latest/quickstart.html). +The changelog is found [here](./CHANGELOG.md). +## Overview +The best way to start a new extractor project is to use the `cogex` CLI. You can install that from PyPI: +``` bash +pip install cognite-extractor-manager +``` +To initialize a new extractor project, run +``` bash +cogex init +``` +in the directory you want your extractor project in. The `cogex` CLI will prompt you for some information about your +project, and then set up a poetry environment, git repository, commit hooks with type and style checks and load a +template. +### Extensions +Some source systems have a lot in common, such as RESTful APIs or systems exposing as MQTT. We therefore have extensions +to `extractor-utils` tailroed to these protocols. These can be found in separate packages: + * [REST extension](https://github.com/cognitedata/python-extractor-utils-rest) + * [MQTT extension](https://github.com/cognitedata/python-extractor-utils-mqtt) +## Contributing +The package is open source under the [Apache 2.0 license](./LICENSE), and contribtuions are welcome. +This project adheres to the [Contributor Covenant v2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/) +as a code of conduct. +### Development environment +We use [poetry](https://python-poetry.org) to manage dependencies and to administrate virtual environments. To develop +`extractor-utils`, follow the following steps to set up your local environment: + 1. [Install poetry](https://python-poetry.org/docs/#installation) if you haven't already. + 2. Clone repository: + ``` + $ git clone git@github.com:cognitedata/python-extractor-utils.git + ``` + 3. Move into the newly created local repository: + ``` + $ cd python-extractor-utils + ``` + 4. Create virtual environment and install dependencies: + ``` + $ poetry install + ``` +### Code requirements +All code must pass [black](https://github.com/ambv/black) and [isort](https://github.com/timothycrosley/isort) style +checks to be merged. It is recommended to install pre-commit hooks to ensure this locally before commiting code: +``` +$ poetry run pre-commit install +``` +Each public method, class and module should have docstrings. Docstrings are written in the [Google +style](https://google.github.io/styleguide/pyguide.html#38-comments-and-docstrings). Please include unit and/or +integration tests for submitted code, and remember to update the [changelog](./CHANGELOG.md). + +%prep +%autosetup -n cognite-extractor-utils-4.3.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-cognite-extractor-utils -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 4.3.1-1 +- Package Spec generated |