# Python3

**URL:** <https://forum.ansible.com/t/python3/12511>\
**Category:** Ansible Project\
**Tags:** rhel, ansible-project\
**Created:** [March 15, 2013, 11:47pm UTC](https://forum.ansible.com/t/python3/12511 "2013-03-15T23:47:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [March 15, 2013, 11:47pm UTC](https://forum.ansible.com/t/python3/12511/1 "2013-03-15T23:47:56Z")

</div>

It does not make any sense porting ansible to Python 3 because you  
would not be following upstream and would be quickly out of date, so I  
don't really understand the rationale. What codebase Ansible is  
written in shouldn't affect your application codebase, or vice versa.

Seeing this really should be about managing nodes, it seems you'd just  
want to make your modules work on 3.x, and there should be zero reason  
you have any problems installing Python 2 on

They are basically different languages, in the end.

There will be a time when we do Python 3, but honestly it's much more  
vital that we can manage a RHEL 5 or 6 guest. It's kind of impossible  
to support 2.4 nodes and 3 at the same time.