# No more remote python-jinja2 dependencies -- all templating now happens on the ansible control machine

**URL:** <https://forum.ansible.com/t/no-more-remote-python-jinja2-dependencies-all-templating-now-happens-on-the-ansible-control-machine/11422>\
**Category:** Ansible Project\
**Tags:** rhel\
**Created:** [April 19, 2012, 2:47am UTC](https://forum.ansible.com/t/no-more-remote-python-jinja2-dependencies-all-templating-now-happens-on-the-ansible-control-machine/11422 "2012-04-19T02:47:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [April 19, 2012, 2:47am UTC](https://forum.ansible.com/t/no-more-remote-python-jinja2-dependencies-all-templating-now-happens-on-the-ansible-control-machine/11422/1 "2012-04-19T02:47:26Z")

</div>

New feature – all tempting now happens on the LOCAL machine, meaning python-jinja2 is no longer a remote dependency.  
This should open up usage on legacy RHEL/CentOS machines that do not have the advantage of pulling python-jinja2 from EPEL  
but still want to make use of Ansible templates.

This means all you need on the remote machines are:

python 2.4 or higher + python-simplejson

OR

python 2.6 or higher (because it includes a json module by default)

Templates will all be run on the control machine in Ansible 0.0.3 (out Monday).

I will update the docs to match!

Coupled with the built-in facts available, dependencies for a fully functional setup (templating+facts) are now very much reduced  
to next to nothing.

–Michael