##// END OF EJS Templates
upstream » ipython
RSS

Clone from https://github.com/ipython/ipython.git

Refactor of coloring and traceback mechanism....
Refactor of coloring and traceback mechanism. This should not change behavior be should slightly clean the code to be a bit more pythonic, and start to introduce methods that avoid side effect (that is to say return values instead of directly writing to stdout). I keep it relatively small and simple for now. My goal is to slowly change the traceback mechanisme to separate buiding the data structure from rendering it to potentially introduce richer tracebacks. Locally I've also started from the other side (re build a traceback rendered from scratch) to see what's needed.
Matthias Bussonnier -
r24334:50b3e0b7
Show More

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.