# trying out newer versions of ansible

**URL:** <https://forum.ansible.com/t/trying-out-newer-versions-of-ansible/19881>\
**Category:** Ansible Project\
**Created:** [November 28, 2015, 12:36am UTC](https://forum.ansible.com/t/trying-out-newer-versions-of-ansible/19881 "2015-11-28T00:36:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Birdsong](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Birdsong](https://forum.ansible.com/u/David_Birdsong)\
**Post date:** [November 28, 2015, 12:36am UTC](https://forum.ansible.com/t/trying-out-newer-versions-of-ansible/19881/1 "2015-11-28T00:36:26Z")

</div>

I’ve been running ansible 1.7.2 for ~year now and I want to take advantage of a bunch of new features like block and fact cacheing.

I pip installed ansible into a virtualenv. Running ansible --version tells me that ansible 2.0 is getting picked up as hoped, but ‘block’ is being rejected as a legal parameter.

Are there changes I need to make to ansible.cfg to block ansible from picking up version 1.7.2 from various module and runners?

---

<div class="post-metadata">

**Author:** ![David\_Birdsong](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Birdsong](https://forum.ansible.com/u/David_Birdsong)\
**Post date:** [November 28, 2015, 1:05am UTC](https://forum.ansible.com/t/trying-out-newer-versions-of-ansible/19881/2 "2015-11-28T01:05:06Z")

</div>

I paid closer attention to running from a git checkout and cleaned up my PYTHONPATH and was able to get 2.0 running and using new syntax.

…always the case after typing up an email asking for help on a project.