##// END OF EJS Templates
Simplify debugger classes....
Simplify debugger classes. Directly get the color scheme from the interactive shell (which is created if not already present, anyways). The goal is ultimately to allow the IPython debugger to be a drop-in replacement of the stdlib pdb with the same signature (in particular, this would obviate the need for plugins such as nose-ipdb and pytest-ipdb; nose and pytest could instead let their `--pdb` command line arg take an argument specifying the Pdb (sub)class to use, e.g. `py.test --pdb=IPython.core.debugger.Pdb`). Also deprecate the `Tracer` class (and related utilities), which can be fairly trivially replaced by `IPython.core.debugger.Pdb().set_trace()` (we can let `Pdb` catch `BdbQuit` itself).
Antony Lee -
r22687:ec2d023d
Show More
Name Size Modified Last Commit Author
/ docs / source / whatsnew
pr
development.rst Loading ...
github-stats-0.11.rst Loading ...
github-stats-0.12.rst Loading ...
github-stats-0.13.rst Loading ...
github-stats-1.0.rst Loading ...
github-stats-2.0.rst Loading ...
github-stats-3.rst Loading ...
github-stats-4.rst Loading ...
github-stats-5.rst Loading ...
index.rst Loading ...
version0.10.rst Loading ...
version0.11.rst Loading ...
version0.12.rst Loading ...
version0.13.rst Loading ...
version0.8.rst Loading ...
version0.9.rst Loading ...
version1.0.rst Loading ...
version2.0.rst Loading ...
version3.rst Loading ...
version3_widget_migration.rst Loading ...
version4.rst Loading ...
version5.rst Loading ...

Documenting What's New

When making a new pull request that either adds a new feature, or makes a
backwards-incompatible change to IPython, please add a new .rst file in this
directory documenting this change as a part of your Pull Request.

This will allow multiple Pull Requests to do the same without conflicting with
one another. Periodically, IPython developers with commit rights will run a
script and populate development.rst
with the contents of this directory, and clean it up.

Files which describe new features can have any name, such as
antigravity-feature.rst, whereas backwards incompatible changes must have
have a filename starting with incompat-, such as
incompat-switching-to-perl.rst. Our "What's new" files always have two
sections, and this prefix scheme will make sure that the backwards incompatible
changes get routed to their proper section.

To merge these files into :file:whatsnew/development.rst, run the script :file:tools/update_whatsnew.py.