From 0ccfbaf51ebd2ebd67773b79659c79e4cd1c00a9 Mon Sep 17 00:00:00 2001 From: CoprDistGit Date: Fri, 5 May 2023 12:29:58 +0000 Subject: automatic import of python-aioemonitor --- .gitignore | 1 + python-aioemonitor.spec | 343 ++++++++++++++++++++++++++++++++++++++++++++++++ sources | 1 + 3 files changed, 345 insertions(+) create mode 100644 python-aioemonitor.spec create mode 100644 sources diff --git a/.gitignore b/.gitignore index e69de29..1cfdbc4 100644 --- a/.gitignore +++ b/.gitignore @@ -0,0 +1 @@ +/aioemonitor-1.0.5.tar.gz diff --git a/python-aioemonitor.spec b/python-aioemonitor.spec new file mode 100644 index 0000000..71e0d8f --- /dev/null +++ b/python-aioemonitor.spec @@ -0,0 +1,343 @@ +%global _empty_manifest_terminate_build 0 +Name: python-aioemonitor +Version: 1.0.5 +Release: 1 +Summary: Asyncio Python lib for SiteSage Emonitor +License: Apache Software License 2.0 +URL: https://github.com/bdraco/aioemonitor +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/e5/ad/3aea32b16aeb0da438d58e59f3252d25747d019a55f92e75313d4bab1d5c/aioemonitor-1.0.5.tar.gz +BuildArch: noarch + +Requires: python3-xmltodict +Requires: python3-aiohttp +Requires: python3-xmltodict +Requires: python3-aiohttp +Requires: python3-pytest-runner +Requires: python3-pytest-asyncio +Requires: python3-black +Requires: python3-codecov +Requires: python3-flake8 +Requires: python3-flake8-debugger +Requires: python3-pytest +Requires: python3-pytest-cov +Requires: python3-pytest-raises +Requires: python3-aioresponses +Requires: python3-bump2version +Requires: python3-coverage +Requires: python3-ipython +Requires: python3-m2r2 +Requires: python3-Sphinx +Requires: python3-sphinx-rtd-theme +Requires: python3-tox +Requires: python3-twine +Requires: python3-wheel +Requires: python3-pytest-runner +Requires: python3-pytest-asyncio +Requires: python3-black +Requires: python3-codecov +Requires: python3-flake8 +Requires: python3-flake8-debugger +Requires: python3-pytest +Requires: python3-pytest-cov +Requires: python3-pytest-raises +Requires: python3-aioresponses +Requires: python3-bump2version +Requires: python3-coverage +Requires: python3-ipython +Requires: python3-m2r2 +Requires: python3-Sphinx +Requires: python3-sphinx-rtd-theme +Requires: python3-tox +Requires: python3-twine +Requires: python3-wheel +Requires: python3-pytest-runner +Requires: python3-pytest-asyncio +Requires: python3-black +Requires: python3-codecov +Requires: python3-flake8 +Requires: python3-flake8-debugger +Requires: python3-pytest +Requires: python3-pytest-cov +Requires: python3-pytest-raises +Requires: python3-aioresponses + +%description +## Features +- Retreive emonitor power status +## Quick Start +```python +import asyncio +import pprint +from aioemonitor import Emonitor +from aiohttp import ClientSession +async def run(): + session = ClientSession() + emonitor = Emonitor("1.2.3.4", session) + status = await emonitor.async_get_status() + pprint.pprint(status) +asyncio.run(run()) +``` +## Installation +**Stable Release:** `pip install aioemonitor`
+**Development Head:** `pip install git+https://github.com/bdraco/aioemonitor.git` +## Documentation +For full package documentation please visit [bdraco.github.io/aioemonitor](https://bdraco.github.io/aioemonitor). +## Development +See [CONTRIBUTING.md](CONTRIBUTING.md) for information related to developing the code. +## The Four Commands You Need To Know +1. `pip install -e .[dev]` + This will install your package in editable mode with all the required development + dependencies (i.e. `tox`). +2. `make build` + This will run `tox` which will run all your tests in both Python 3.7 + and Python 3.8 as well as linting your code. +3. `make clean` + This will clean up various Python and build generated files so that you can ensure + that you are working in a clean environment. +4. `make docs` + This will generate and launch a web browser to view the most up-to-date + documentation for your Python package. +#### Additional Optional Setup Steps: +- Turn your project into a GitHub repository: + - Make an account on [github.com](https://github.com) + - Go to [make a new repository](https://github.com/new) + - _Recommendations:_ + - _It is strongly recommended to make the repository name the same as the Python + package name_ + - _A lot of the following optional steps are *free* if the repository is Public, + plus open source is cool_ + - After a GitHub repo has been created, run the commands listed under: + "...or push an existing repository from the command line" +- Register your project with Codecov: + - Make an account on [codecov.io](https://codecov.io)(Recommended to sign in with GitHub) + everything else will be handled for you. +- Ensure that you have set GitHub pages to build the `gh-pages` branch by selecting the + `gh-pages` branch in the dropdown in the "GitHub Pages" section of the repository settings. + ([Repo Settings](https://github.com/bdraco/aioemonitor/settings)) +- Register your project with PyPI: + - Make an account on [pypi.org](https://pypi.org) + - Go to your GitHub repository's settings and under the + [Secrets tab](https://github.com/bdraco/aioemonitor/settings/secrets/actions), + add a secret called `PYPI_TOKEN` with your password for your PyPI account. + Don't worry, no one will see this password because it will be encrypted. + - Next time you push to the branch `main` after using `bump2version`, GitHub + actions will build and deploy your Python package to PyPI. +#### Suggested Git Branch Strategy +1. `main` is for the most up-to-date development, very rarely should you directly + commit to this branch. GitHub Actions will run on every push and on a CRON to this + branch but still recommended to commit to your development branches and make pull + requests to main. If you push a tagged commit with bumpversion, this will also release to PyPI. +2. Your day-to-day work should exist on branches separate from `main`. Even if it is + just yourself working on the repository, make a PR from your working branch to `main` + so that you can ensure your commits don't break the development head. GitHub Actions + will run on every push to any branch or any pull request from any branch to any other + branch. +3. It is recommended to use "Squash and Merge" commits when committing PR's. It makes + each set of changes to `main` atomic and as a side effect naturally encourages small + well defined PR's. +**Apache Software License 2.0** + +%package -n python3-aioemonitor +Summary: Asyncio Python lib for SiteSage Emonitor +Provides: python-aioemonitor +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-aioemonitor +## Features +- Retreive emonitor power status +## Quick Start +```python +import asyncio +import pprint +from aioemonitor import Emonitor +from aiohttp import ClientSession +async def run(): + session = ClientSession() + emonitor = Emonitor("1.2.3.4", session) + status = await emonitor.async_get_status() + pprint.pprint(status) +asyncio.run(run()) +``` +## Installation +**Stable Release:** `pip install aioemonitor`
+**Development Head:** `pip install git+https://github.com/bdraco/aioemonitor.git` +## Documentation +For full package documentation please visit [bdraco.github.io/aioemonitor](https://bdraco.github.io/aioemonitor). +## Development +See [CONTRIBUTING.md](CONTRIBUTING.md) for information related to developing the code. +## The Four Commands You Need To Know +1. `pip install -e .[dev]` + This will install your package in editable mode with all the required development + dependencies (i.e. `tox`). +2. `make build` + This will run `tox` which will run all your tests in both Python 3.7 + and Python 3.8 as well as linting your code. +3. `make clean` + This will clean up various Python and build generated files so that you can ensure + that you are working in a clean environment. +4. `make docs` + This will generate and launch a web browser to view the most up-to-date + documentation for your Python package. +#### Additional Optional Setup Steps: +- Turn your project into a GitHub repository: + - Make an account on [github.com](https://github.com) + - Go to [make a new repository](https://github.com/new) + - _Recommendations:_ + - _It is strongly recommended to make the repository name the same as the Python + package name_ + - _A lot of the following optional steps are *free* if the repository is Public, + plus open source is cool_ + - After a GitHub repo has been created, run the commands listed under: + "...or push an existing repository from the command line" +- Register your project with Codecov: + - Make an account on [codecov.io](https://codecov.io)(Recommended to sign in with GitHub) + everything else will be handled for you. +- Ensure that you have set GitHub pages to build the `gh-pages` branch by selecting the + `gh-pages` branch in the dropdown in the "GitHub Pages" section of the repository settings. + ([Repo Settings](https://github.com/bdraco/aioemonitor/settings)) +- Register your project with PyPI: + - Make an account on [pypi.org](https://pypi.org) + - Go to your GitHub repository's settings and under the + [Secrets tab](https://github.com/bdraco/aioemonitor/settings/secrets/actions), + add a secret called `PYPI_TOKEN` with your password for your PyPI account. + Don't worry, no one will see this password because it will be encrypted. + - Next time you push to the branch `main` after using `bump2version`, GitHub + actions will build and deploy your Python package to PyPI. +#### Suggested Git Branch Strategy +1. `main` is for the most up-to-date development, very rarely should you directly + commit to this branch. GitHub Actions will run on every push and on a CRON to this + branch but still recommended to commit to your development branches and make pull + requests to main. If you push a tagged commit with bumpversion, this will also release to PyPI. +2. Your day-to-day work should exist on branches separate from `main`. Even if it is + just yourself working on the repository, make a PR from your working branch to `main` + so that you can ensure your commits don't break the development head. GitHub Actions + will run on every push to any branch or any pull request from any branch to any other + branch. +3. It is recommended to use "Squash and Merge" commits when committing PR's. It makes + each set of changes to `main` atomic and as a side effect naturally encourages small + well defined PR's. +**Apache Software License 2.0** + +%package help +Summary: Development documents and examples for aioemonitor +Provides: python3-aioemonitor-doc +%description help +## Features +- Retreive emonitor power status +## Quick Start +```python +import asyncio +import pprint +from aioemonitor import Emonitor +from aiohttp import ClientSession +async def run(): + session = ClientSession() + emonitor = Emonitor("1.2.3.4", session) + status = await emonitor.async_get_status() + pprint.pprint(status) +asyncio.run(run()) +``` +## Installation +**Stable Release:** `pip install aioemonitor`
+**Development Head:** `pip install git+https://github.com/bdraco/aioemonitor.git` +## Documentation +For full package documentation please visit [bdraco.github.io/aioemonitor](https://bdraco.github.io/aioemonitor). +## Development +See [CONTRIBUTING.md](CONTRIBUTING.md) for information related to developing the code. +## The Four Commands You Need To Know +1. `pip install -e .[dev]` + This will install your package in editable mode with all the required development + dependencies (i.e. `tox`). +2. `make build` + This will run `tox` which will run all your tests in both Python 3.7 + and Python 3.8 as well as linting your code. +3. `make clean` + This will clean up various Python and build generated files so that you can ensure + that you are working in a clean environment. +4. `make docs` + This will generate and launch a web browser to view the most up-to-date + documentation for your Python package. +#### Additional Optional Setup Steps: +- Turn your project into a GitHub repository: + - Make an account on [github.com](https://github.com) + - Go to [make a new repository](https://github.com/new) + - _Recommendations:_ + - _It is strongly recommended to make the repository name the same as the Python + package name_ + - _A lot of the following optional steps are *free* if the repository is Public, + plus open source is cool_ + - After a GitHub repo has been created, run the commands listed under: + "...or push an existing repository from the command line" +- Register your project with Codecov: + - Make an account on [codecov.io](https://codecov.io)(Recommended to sign in with GitHub) + everything else will be handled for you. +- Ensure that you have set GitHub pages to build the `gh-pages` branch by selecting the + `gh-pages` branch in the dropdown in the "GitHub Pages" section of the repository settings. + ([Repo Settings](https://github.com/bdraco/aioemonitor/settings)) +- Register your project with PyPI: + - Make an account on [pypi.org](https://pypi.org) + - Go to your GitHub repository's settings and under the + [Secrets tab](https://github.com/bdraco/aioemonitor/settings/secrets/actions), + add a secret called `PYPI_TOKEN` with your password for your PyPI account. + Don't worry, no one will see this password because it will be encrypted. + - Next time you push to the branch `main` after using `bump2version`, GitHub + actions will build and deploy your Python package to PyPI. +#### Suggested Git Branch Strategy +1. `main` is for the most up-to-date development, very rarely should you directly + commit to this branch. GitHub Actions will run on every push and on a CRON to this + branch but still recommended to commit to your development branches and make pull + requests to main. If you push a tagged commit with bumpversion, this will also release to PyPI. +2. Your day-to-day work should exist on branches separate from `main`. Even if it is + just yourself working on the repository, make a PR from your working branch to `main` + so that you can ensure your commits don't break the development head. GitHub Actions + will run on every push to any branch or any pull request from any branch to any other + branch. +3. It is recommended to use "Squash and Merge" commits when committing PR's. It makes + each set of changes to `main` atomic and as a side effect naturally encourages small + well defined PR's. +**Apache Software License 2.0** + +%prep +%autosetup -n aioemonitor-1.0.5 + +%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-aioemonitor -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot - 1.0.5-1 +- Package Spec generated diff --git a/sources b/sources new file mode 100644 index 0000000..171f0c7 --- /dev/null +++ b/sources @@ -0,0 +1 @@ +f358733baa4e670fa623482515ce8e9b aioemonitor-1.0.5.tar.gz -- cgit v1.2.3