Also: comment #2 describes the workaround accurately. A user is now apparently expected to also specify they want the py3 variant package along with the juju-deployer package. We've done that in OSCI and have no further issues.
Also: comment #2 describes the workaround accurately. A user is now apparently expected to also specify they want the py3 variant package along with the juju-deployer package. We've done that in OSCI and have no further issues.