On Tue, Nov 1, 2016 at 9:30 AM, Marco Ceppi
wrote:
> This is really one of the goals. python-jujuclient, amulet, and even to an
> extent deployer all poorly implement an abstraction to Juju. These will all
> eventually fall away in favor of a consolidated, focused,
This is really one of the goals. python-jujuclient, amulet, and even to an
extent deployer all poorly implement an abstraction to Juju. These will all
eventually fall away in favor of a consolidated, focused, well built Object
Oriented Python library.
Marco
On Tue, Nov 1, 2016, 4:25 PM Ryan
This is good stuff. I think keeping it focused on Juju 2.0 and later,
completely free of legacy shims, is a good thing. I'd love to be using
this natively instead of the collective stack of [Amulet + Juju-deployer +
python-jujuclient], and plan to take it for a spin.
Cheers,
Ryan
On Tue, Nov
Hi everyone,
We've been working on a new python client for Juju. It's still in
development,
but we wanted to share the first bits to illicit feedback:
https://github.com/juju/python-libjuju
Features of this library include:
* fully asynchronous - uses asyncio and async/await features of python