Comment 8 for bug 1219223

Hi, I'd also like to be of assistance here. Scott, reading this bug and bug 1247132, I'm not sure where I could help right now - are you suggesting that we need to support cheetah-compatbile syntax in python3 port? Or are you suggesting that we support different template syntax as a default for the python3 port?
The first option seems unlikely to happen, since cheetah upstream is dead and I don't know any templating engine that would be fully compatible with cheetah. The second option would be, in my eyes, very confusing, since I'd expect the same beheviour regardless of Python version I run cloud-init with.
What I'm trying to say is, we should decide to switch to another templating engine (e.g. mako) and stick with it.
Or we could do a compromise and support both mako and cheetah for Python 2 and only mako for Python 3 (and differentiate between them e.g. based on file extension or sth. like that).

Would that be acceptable?
Thanks!