Is there a roadmap for creating a fork of pylxd for incus (pyincus I assume)?

[Blue_Falcon]

These are lazy projects, but a foot in the door:

Moving to Incus for users of pylxd

Ok, so I’ve written 2 sets of tooling for this: pyincusd pypi package: GitHub - anonhostpi/pyincusd · GitHub incusd example client: GitHub - anonhostpi/incusd-client · GitHub The example client is a full OOP client wrapper around pyincusd. I have not included it in pyincusd or shipped it as its own package as the maintenance requirements are higher. pyincusd is significantly easier to maintain, because it is just CI/CD. It calls an OpenAPI client generator nightly when it detects a new versio…

I can reasonably maintain pyincusd myself, as its designed to be low maintenance as hell.

For incusd-client, its first pass is full-encompassing, but untested. Neither ships with tests. I have identified that while incusd-client is mostly well-written, its not something I can maintain easy (which is why I haven’t included it in pyincusd or shipped it as its own python package)

Open to PRs and/or discussing maintenance turnover.