# V2 is live **URL:** \ **Category:** Ansible Project\ **Created:** [June 2, 2015, 1:18am UTC](https://forum.ansible.com/t/v2-is-live/18374 "2015-06-02T01:18:41Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\ **Post date:** [June 2, 2015, 1:18am UTC](https://forum.ansible.com/t/v2-is-live/18374/1 "2015-06-02T01:18:41Z")
Hi all, the transition on devel to the v2 codebase is complete. If you run into any problems and want to switch back to using the old v1 codebase from a git checkout, simply source the hacking script in the v1 directory instead: $ . v1/hacking/env-setup As always if and when you find any bugs, you can either open an issue directly on Github or ping us on the ansible-devel mailing list or in #ansible-devel on Freenode. Thanks! ---
**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\ **Post date:** [June 2, 2015, 8:10am UTC](https://forum.ansible.com/t/v2-is-live/18374/2 "2015-06-02T08:10:44Z")
Congratulations on reaching this milestone. Jon ---
**Author:** ![Bob\_Tanner](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Bob\_Tanner](https://forum.ansible.com/u/Bob_Tanner)\ **Post date:** [June 4, 2015, 5:55am UTC](https://forum.ansible.com/t/v2-is-live/18374/3 "2015-06-04T05:55:42Z")
Before I pollute the issue tracker, cannot get v1 code to source properly. $ git show commit 0826106441d15820d086c1c9eaf6242aa80e4406 Author: Brian Coca \*\*snip\*\*@gmail.com $ ansible --version ansible 2.0.0 (devel 0826106441) last updated 2015/06/03 21:55:07 (GMT -500) lib/ansible/modules/core: (detached HEAD b138411671) last updated 2015/06/03 00:37:46 (GMT -500) lib/ansible/modules/extras: (detached HEAD 1276420a3a) last updated 2015/06/03 00:37:50 (GMT -500) v1/ansible/modules/core: (detached HEAD f8d8af17cd) last updated 2015/06/03 00:37:54 (GMT -500) v1/ansible/modules/extras: (detached HEAD 495ad450e5) last updated 2015/06/03 00:37:58 (GMT -500) configured module search path = None $ source v1/hacking/env-setup python: can’t open file ‘setup.py’: [Errno 2] No such file or directory Setting up Ansible to run out of checkout… Problem is in gen\_egg\_info(). $ANSIBLE\_HOME is set to /path/ansible/v1 but the setup.py is in /path/ansible. I just copied the setup.py into v1 and the source works. But I don’t know if that is the right solution or the right way to solve the problem. And now all my v1 plays throw AttributeError: ‘module’ object has no attribute ‘DEFAULT\_SELINUX\_SPECIAL\_FS’ ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [June 4, 2015, 5:57pm UTC](https://forum.ansible.com/t/v2-is-live/18374/4 "2015-06-04T17:57:08Z")
Bob, We just synced the v1 directory with the v1\_last branch to resolve the AttributeError. I don’t believe the setup.py issue should affect things, or at least it hasn’t affected anything for me. ---
**Author:** ![Bob\_Tanner](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Bob\_Tanner](https://forum.ansible.com/u/Bob_Tanner)\ **Post date:** [June 4, 2015, 9:56pm UTC](https://forum.ansible.com/t/v2-is-live/18374/5 "2015-06-04T21:56:06Z")
Many do I hate top posting. Opened an issue before I read your post. [https://github.com/ansible/ansible/issues/11171](https://github.com/ansible/ansible/issues/11171) Still getting: $ source v1/hacking/env-setup python: can’t open file ‘setup.py’: [Errno 2] No such file or directory But my v1 playbooks and plays are working now. ---
**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\ **Post date:** [June 5, 2015, 2:33pm UTC](https://forum.ansible.com/t/v2-is-live/18374/6 "2015-06-05T14:33:17Z")
When we had v2 in a separate directory I commented out the setup.py stuff from the env-setup script. Not sure if that will work here or not. The v1/bin/ansible\* scripts need to find some egg\_info for ansible but chances are it doesn’t need to find a specific version. Maybe the best plan is to copy a generated egg\_info tree into the v1 directory and comment out the setup.py call. -Toshio