Avoid broken backwards compatibility by switching to new interface.  Require urwid 1.1.1.
Be more serious about Debugger being a singleton. Only load breakpoints once.
Install scripts pudb (or pudb3 for Python 3) with setup.py

These work exactly the same as python -m pudb.run.
Fix setup.py to work in Python 2.4
Merge pull request #54 from asmeurer/console_scripts

Install scripts pudb (or pudb3 for Python 3) with setup.py
Catch I/O errors in readline setup.
Add 256 color support to syntax highlighting.
Insert 2to3 invocation into setup.py.
Revert "Insert 2to3 invocation into setup.py."

This reverts commit 4f913f6d7d4cb0bd5d6e4e09b322a4382c72badc,
in accordance with the decision [1] to not use 2to3.

[1] https://github.com/inducer/pudb/pull/1
Fix Python 2-ism in exception catching.

Proper Py2/3 fix pointed out by Aaron Meurer.
Update README to mention `pudb` script
Mention pull requests
Merge pull request #60 from asmeurer/readme

Small updates to the README
Allow saving the current traceback to a text file.
Don't crash when on '.' and ',' with no last search. Fixes #62.
Add support for __version__. (suggested by Luke Lee)
Add .mailmap

Now git shortlog -ns has no duplicates. Also, I wanted an excuse to exercise
my push access :)
Add .DS_Store to .gitignore
Enable Control-C to pause the debugger

This fixes #42.  Now pressing Control-C while the script is running enters the
debugger in the line that was run (i.e., it does a set_trace()).

Note that this only works if the script was invoked from `pudb` or `python -m
pudb`.  If PuDB was started with `import pudb; pudb.set_trace()`, this does
not work.  But not that even without this patch, Control-C kills Python
entirely in that case (as opposed to entering post-mortem mode).
Fix up some more of the interrupt framework

This (partially) fixes #31, and also improves work on #42.

Now, interrupting with Control-C works when the debugging is started with
set_trace().

The SIGINT handler is enabled via the public function
pudb.set_interrupt_handler.  If you want to be able to enter PuDB from within
your application, just call this function.  By default, it uses SIGINT (i.e.,
Control-C), but you can change it to use a different signal if that one
interferes.

There is still one major issue, which is that when you break in the middle of
an atomic operation, it goes to bdb. After pressing `n` several times you get
to your code, though.