Three problem here is that on a system without Python 2 this will just fail.
As there, nothing is named Python. Virtual env does somewhat of a disservice by
providing python 3 as python.
I agree that generally this is a pain. We should have some way to tell cloud
init which python to use.
Joshua Harlow has proposed merging ~harlowja/cloud-init:yaml-check-python into
cloud-init:master.
Requested reviews:
cloud init development team (cloud-init-dev)
For more details, see:
https://code.launchpad.net/~harlowja/cloud-init/+git/cloud-init/+merge/307996
--
Your team cloud init
2 matches
Mail list logo
