[ynak]

Do they have any plans to support python3? I want to use it on Arch and Ubuntu. FAQ says they will address this issue by python3 becomes mainstream, but what does the mainstream exactly mean? When RHEL set python3 as default? Python2 maintenance continues until 2020, so seems have to wait for more several years.

[jimi_c]

Hi ynak, we're planning on supporting py3 in the core engine with the v2 codebase. As for modules, we're still working on the best possible solution there, since we do need to continue supporting python 2.4 for the foreseeable future.

[Spiritus]

Why would you need to support Python 2.4? Haven't that been dead for for like 10 years?

[jimi_c]

There are still a lot of RHEL/CentOS 5 users out there, which run python 2.4. While py3 is moving forward, the number of users stuck on 2.4 is still considerably larger, and we will continue to support that until such a time as it's no longer the case. In the meantime, we are exploring options so that we can help those on newer distributions work by default in the same way.

[ynak]

Thank you for the reply. I'm looking forward to it.

[CraigJPerry]

Those distributions have great dependency management, they will install the python 2 dependency when installing ansible

[berdario]

This does not help when you want to manage Arch or Ubuntu machines, since you're not installing ansible there, you're just letting ansible connect with ssh and execute Python2 scripts.

So, before being able to run your playbooks to do your provisioning/deployment, now you have to handle credentials outside of ansible, connect to the remote machine manually and install an old version of Python.

It's only a minor annoyance for me, but it could get worse.

[Sgoettschkes]

You can always use ansible ad-hoc tasks for this. There is the `raw` module which doesn't use python and just executes code.