Go to file
2012-01-10 16:27:38 -05:00
pudb Deal with incompatible change in IPy 0.12 API. 2012-01-10 16:27:38 -05:00
test Implement and debug the programming interface to match pdb. 2009-07-09 19:54:34 -04:00
.gitignore Add distribute files that setup.py downloads to the .gitignore file 2011-07-26 22:42:24 -06:00
debug_me.py Fix stripping of initial newline from source. 2009-09-11 09:50:00 -04:00
distribute_setup.py Update distribute_setup.py. 2011-07-27 18:47:36 -04:00
example-stringifier.py Update run_with_timeout docstring 2011-08-09 05:22:50 -06:00
example-theme.py Add saved settings, themes, etc. 2011-02-13 22:18:36 -05:00
MANIFEST.in Bump urwid version. Add README to MANIFEST.in. 2011-08-29 23:20:48 +02:00
README.rst Make README as suggested by Aaron, read from setup.py for long_description. 2011-07-29 11:19:59 -04:00
setup.py Bump urwid version. Add README to MANIFEST.in. 2011-08-29 23:20:48 +02:00
try-the-debugger.sh Fix the try-the-debugger script. 2009-06-20 22:11:51 -04:00

PuDB is a full-screen, console-based visual debugger for Python. 

Its goal is to provide all the niceties of modern GUI-based debuggers in a 
more lightweight and keyboard-friendly package. PuDB allows you to debug code 
right where you write and test it--in a terminal. If you've worked with the 
excellent (but nowadays ancient) DOS-based Turbo Pascal or C tools, PuDB's UI 
might look familiar.

Here's a screenshot:

.. image:: http://tiker.net/pub/pudb-screenshot.png

You may watch a `screencast <http://vimeo.com/5255125>`_, too.

Features
--------

* Syntax-highlighted source, the stack, breakpoints and variables are all 
  visible at once and continuously updated. This helps you be more aware of 
  what's going on in your program. Variable displays can be expanded, collapsed 
  and have various customization options.

* Simple, keyboard-based navigation using single keystrokes makes debugging 
  quick and easy. PuDB understands cursor-keys and Vi shortcuts for navigation. 
  Other keys are inspired by the corresponding pdb coomands.

* Use search to find relevant source code, or use "m" to invoke the module 
  browser that shows loaded modules, lets you load new ones and reload existing 
  ones.

* Breakpoints can be set just by pointing at a source line and hitting "b" and 
  then edited visually in the breakpoints window.  Or hit "t" to run to the line 
  under the cursor.

* Drop to a Python shell in the current environment by pressing "!".

* PuDB places special emphasis on exception handling. A post-mortem mode makes 
  it easy to retrace a crashing program's last steps.

* IPython integration (see `wiki <http://wiki.tiker.net/PuDB>`_)

Installing
----------

Install PuDB using the command::

    easy_install pudb

Getting Started
---------------

To start debugging, simply insert::

    from pudb import set_trace; set_trace()

into the piece of code you want to debug, or run the entire script with::

    python -m pudb.run my-script.py

Documentation and Support
-------------------------

PuDB has a `wiki <http://wiki.tiker.net/PuDB>`_, where documentation and
debugging wisdom are collected.

PuDB also has a `mailing list <http://lists.tiker.net/listinfo/pudb>`_ that
you may use to submit patches and requests for help.

Programming PuDB
----------------

At the programming language level, PuDB displays the same interface
as Python's built-in `pdb module <http://docs.python.org/library/pdb.html>`_.
Just replace `pdb` with `pudb`. 
(One exception: `run` is called `runstatement`.)

License and Dependencies
------------------------

PuDB is distributed under the MIT license. It relies on the following
excellent pieces of software:

* Ian Ward's `urwid <http://excess.org/urwid>`_ console UI library
* Georg Brandl's `pygments <http://pygments.org>`_ syntax highlighter

Development Version
-------------------

You may obtain the development version using the `Git <http://git-scm.org/>`_
version control tool.::

    git clone http://git.tiker.net/trees/pudb.git

You may also `browse the code <http://git.tiker.net/pudb.git>`_ online.

FAQ
---

**Q: I navigated to the Variables/Stack/Breakpoints view.  How do I get
back to the source view?**

A: Press your left arrow key.