1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
|
# aioemonitor
[](https://github.com/bdraco/aioemonitor/actions)
[](https://bdraco.github.io/aioemonitor/)
[](https://codecov.io/gh/bdraco/aioemonitor)
Asyncio Python lib for SiteSage Emonitor
---
## 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`<br>
**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**
|
