PyDoover: The Python Package for Doover
PyDoover is a Python package that provides a simple and easy-to-use interface for using the Doover platform on devices, in tasks and CLIs.
Quick Links
Installing
Python 3.11 or higher is required
# Using UV
uv add pydoover
# Using pip
pip install -U pydoover
# to install the development version:
pip install -U git+https://github.com/getdoover/pydoover
If you are using pydoover and need grpc support and are not using the doover_device_base docker image, install the grpc optional dependencies:
We currently use grpcio==1.65.1 across all our services, so you need to install this version of grpcio to avoid issues.
uv add pydoover[grpc]
# or
pip install -U pydoover[grpc]
Debian Package
The pydoover package (in particular CLI) is also available as a Debian package. You can install it using the following command:
# add the Doover apt repository:
sudo wget http://apt.u.doover.com/install.sh -O - | sh
# install the package
sudo apt install doover-pydoover
Development
To install all dependencies for development, install all optional dependencies (grpc, reports, test, etc.), run:
uv sync --all-extras --all-groups
We use pre-commit hooks to ensure code quality and consistency using Ruff. To set up pre-commit hooks, run the following command:
pre-commit install
To run unit tests, use pytest in the main directory of the repository:
uv run pytest
Documentation
The documentation for PyDoover is generated using Sphinx and can be found in the docs directory. To build the documentation, run:
uv sync --all-extras --all-groups # ensure all dependencies are installed
cd docs
make html
Contributing
For more information, please reach out to the maintainers at hello@doover.com
License
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
Metadata
Release files for pydoover 1.18.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pydoover-1.18.6.tar.gz | 645.0 kB | Without provenance | Details for pydoover-1.18.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pydoover-1.18.6-py3-none-any.whl | Python 3 | none | any | Details for pydoover-1.18.6-py3-none-any.whl |
Total release size: 989.9 kB
Release files / pydoover-1.18.6.tar.gz
| Download URL | pydoover-1.18.6.tar.gz |
|---|---|
| Size | 645.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9bfb4f38f60d83280680416583ab507ef3b9676f36ff648fef5c586bfe0f16fe
|
|
BLAKE2b-256 checksum How to use checksums |
98ba9a655ba913a3fcc75b90de8080b0ac276252ec4f2ae1c0f0eaad50a731ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / pydoover-1.18.6-py3-none-any.whl
| Download URL | pydoover-1.18.6-py3-none-any.whl |
|---|---|
| Size | 344.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
515ce034ba6f3ab120da6ed771c1238a120fdc2220676197ab140f64a1662299
|
|
BLAKE2b-256 checksum How to use checksums |
61ba7fa094edcb8af062f56cdd82cfe23082ca93d4390fa91d84ee8dc2ba26e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for pydoover 1.18.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.