| 1 |
Source: aiodukeenergy |
| 2 |
Maintainer: Home Assistant Team <[email protected]> |
| 3 |
Uploaders: |
| 4 |
Edward Betts <[email protected]>, |
| 5 |
Section: python |
| 6 |
Build-Depends: |
| 7 |
debhelper-compat (= 13), |
| 8 |
dh-sequence-python3, |
| 9 |
dh-sequence-sphinxdoc <!nodoc>, |
| 10 |
pybuild-plugin-pyproject, |
| 11 |
python3-all, |
| 12 |
python3-poetry-core, |
| 13 |
Build-Depends-Indep: |
| 14 |
furo <!nodoc>, |
| 15 |
python3-aiohttp <!nocheck>, |
| 16 |
python3-aioresponses <!nocheck>, |
| 17 |
python3-jwt <!nocheck>, |
| 18 |
python3-myst-parser <!nodoc>, |
| 19 |
python3-pytest <!nocheck>, |
| 20 |
python3-pytest-asyncio <!nocheck>, |
| 21 |
python3-pytest-cov <!nocheck>, |
| 22 |
python3-sphinx <!nodoc>, |
| 23 |
python3-sphinx-autobuild <!nodoc>, |
| 24 |
python3-yarl <!nocheck>, |
| 25 |
Standards-Version: 4.7.3 |
| 26 |
Homepage: https://github.com/hunterjm/aiodukeenergy |
| 27 |
Vcs-Browser: https://salsa.debian.org/homeassistant-team/deps/aiodukeenergy |
| 28 |
Vcs-Git: https://salsa.debian.org/homeassistant-team/deps/aiodukeenergy.git |
| 29 |
Testsuite: autopkgtest-pkg-pybuild |
| 30 |
|
| 31 |
Package: python3-aiodukeenergy |
| 32 |
Architecture: all |
| 33 |
Depends: |
| 34 |
${misc:Depends}, |
| 35 |
${python3:Depends}, |
| 36 |
${sphinxdoc:Depends}, |
| 37 |
Built-Using: |
| 38 |
${sphinxdoc:Built-Using}, |
| 39 |
Description: Asyncio-based library for interacting with Duke Energy's services |
| 40 |
This library provides asynchronous capabilities to access and interact with |
| 41 |
Duke Energy's services efficiently. Designed to handle multiple data requests |
| 42 |
and responses asynchronously, it enables users to retrieve and process energy |
| 43 |
consumption data, account information, and billing details from Duke Energy. |
| 44 |
By utilizing this library, applications can perform complex data operations in |
| 45 |
a non-blocking manner, thus enhancing performance when dealing with energy |
| 46 |
data queries and other service interactions. This is especially beneficial in |
| 47 |
context where quick data access and response is necessary, such as monitoring |
| 48 |
applications or data analysis tools. |