# UserWarning: Module ansible was already imported

**URL:** <https://forum.ansible.com/t/userwarning-module-ansible-was-already-imported/16484>\
**Category:** Ansible Developer\
**Created:** [October 10, 2014, 8:57am UTC](https://forum.ansible.com/t/userwarning-module-ansible-was-already-imported/16484 "2014-10-10T08:57:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Strahinja\_Kustudic2](https://avatars.discourse-cdn.com/v4/letter/s/b4bc9f/32.png) [@Strahinja\_Kustudic2](https://forum.ansible.com/u/Strahinja_Kustudic2)\
**Post date:** [October 10, 2014, 8:57am UTC](https://forum.ansible.com/t/userwarning-module-ansible-was-already-imported/16484/1 "2014-10-10T08:57:46Z")

</div>

I just cloned the ansible repo, tried sourcing hacking/env-setup and this is the warning I get when I run ansible --version:

`  
**$ source hacking/env-setup**

Setting up Ansible to run out of checkout…

PATH=/home/vagrant/tmp/ansible/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/home/vagrant/bin  
PYTHONPATH=/home/vagrant/tmp/ansible/lib:  
MANPATH=/home/vagrant/tmp/ansible/docs/man:

Remember, you may wish to specify your host file with -i

Done!

**$ ansible --version**  
/usr/lib64/python2.6/site-packages/jinja2/ **init**.py:31: UserWarning: Module ansible was already imported from /home/vagrant/tmp/ansible/lib/ansible/ **init**.pyc, but /usr/lib/python2.6/site-packages is being added to sys.path  
**version** = **import** (‘pkg\_resources’)   
ansible 1.8 (devel d19fe8d95d) last updated 2014/10/10 10:39:37 (GMT +200)  
lib/ansible/modules/core: (detached HEAD 5af8d55b03) last updated 2014/10/10 10:39:41 (GMT +200)  
lib/ansible/modules/extras: (detached HEAD 8a4f07eecd) last updated 2014/10/10 10:39:46 (GMT +200)  
v2/ansible/modules/core: (detached HEAD cb69744bce) last updated 2014/10/10 10:39:51 (GMT +200)  
v2/ansible/modules/extras: (detached HEAD 8a4f07eecd) last updated 2014/10/10 10:39:56 (GMT +200)  
configured module search path = /usr/share/ansible

`

I don’t remember seeing this before the modules were moved to separate repositories. Does the env-setup script need updating?
