Embed a Python interpreter within the unit agent binaries

Good questions. I noticed that someone had added this line of advice in First steps with the Operator Framework.

Check that the top of the charm.py contains #!/usr/bin/env python3 .

It strikes me that if we’re concerned that charms might be executed by the wrong interpreter, perhaps we should take that problem away by design?

Must admit that this isn’t a fully-fledged idea by any means!