edcaed537a
Very few calls at client side really needs VM class name. So, even in non-blind mode use just QubesVM class, to avoid strange cases depending on blind mode being enabled or not. Then, have VM class name in 'klass' property. If known at object creation time, cache it, otherwise query qubesd at first access. |
||
---|---|---|
ci | ||
debian | ||
doc | ||
etc | ||
qubesadmin | ||
rpm_spec | ||
test-packages | ||
.gitignore | ||
.travis.yml | ||
LICENSE | ||
Makefile | ||
Makefile.builder | ||
README.md | ||
run-tests | ||
setup.py | ||
version |
This is client side implementation of Qubes Admin API. See https://www.qubes-os.org/doc/admin-api/ for protocol specification.
Compatibility
Most of the API modules are compatible with Python >= 2.7. Very few parts require Python >= 3.4:
- tools (
qvm-*
) - qubesadmin.events module (for asyncio module)
Parts not compatible with Python < 3.4, are not installed in such environment.