# (developers) Tips on using debuggers with Ansible

**URL:** <https://forum.ansible.com/t/developers-tips-on-using-debuggers-with-ansible/12076>\
**Category:** Ansible Project\
**Created:** [November 10, 2012, 1:27pm UTC](https://forum.ansible.com/t/developers-tips-on-using-debuggers-with-ansible/12076 "2012-11-10T13:27: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:** [November 10, 2012, 1:27pm UTC](https://forum.ansible.com/t/developers-tips-on-using-debuggers-with-ansible/12076/1 "2012-11-10T13:27:26Z")

</div>

As promised on one ticket, here's a bit of info about how to use  
debuggers with Ansible.

[http://michaeldehaan.net/post/35403909347/](http://michaeldehaan.net/post/35403909347/)

TLDR: "pip install epdb" is good, and test with use "--forks 1".

(You can still use regular pdb locally with ansible and --forks 1, but  
it's not so good with testing module execution)