Updating the what's new for this branch.

Fix in MPI psum example. Thanks to J. Thomas for updating the psum example to the mpi4py 1.1.0 API.

Added test for the pretty.py extension and fixed sphinx docs. * The pretty.py extension now has a proper test, although it is minimal. * The latex/pdf Sphinx docs were building as a *single* chapter. The fix was to add a 6th argument of True to the latex_documents entry in conf.py

Completed work on pretty.py extension. There is still not any testing, but I have to move on...

The pretty.py extension has been ported to the new extension API. I have also cleaned up the extension API to enable extension unloading and have added magics for working with extensions: * %load_ext * %reload_ext * %unload_ext

Fixing zero-install ipython.py script.

Updating the What's new section of the docs with the summer's work.

Merging the config-refactor branch. This branch did start with the config system refactor, but moved on from there. Here are some highlights. * New config system. * Traitlets * Componenets * Applications * The main ipython program has been refactored to use these new abstractions.

Major work on the documentation. * Everything is cleaned up. * Outdated things have been re-written or removed. * Full documentation about the new config system has been added. * The developer guide has been re-organized and re-written where appropriate.

Work on documentation. * Reorganizing material everywhere. * Consolidating material in config and development. We had lots of repeated material in development. * Removing or fixing outdated or incorrect material.

Cleanup of docs. * Updated all of the sphinx extensions from sampledoc. * Using mpl versions of extensions they ship. * Using nice theme of sampledoc. * Reorganizing our docs.

Changed Component.__init__ so that config is not deepcopy'd. Previously, we were deepcoping the config for each component. This causes overhead and it is not clear at this point that having components share config (by reference) is a bad idea.

Transformers have been added to the prefilter. Transformers are run first before the checkers/handlers and simple transform lines of input. In the long run, we are going to move away from checkers/handlers and just use transformers. The new transformers are used to implement the a=!ls and b=%who syntax.

pyparsing 1.5.2 added to externals. This opens the door for doing more complex prefilter operations using pyparsing. Wohoo!

First failed attempt to get the test suite to run.

Fixing minor bug with the logging level in ipapp.py.

Removed ipapi compatability layer and updated top-level functions. The ipapi.py module has been completely deprecated as of this point. No new code should use it and all existing code that uses it will migrate away from it. The launch_new_instance function has been moved to ipapp and the setup.py scripts have been updated.

Updated Michele Simionato's decorator.py module to 3.1.2. I also moved it to external/decorator.py

Moving extensions to either quarantine or deathrow. When a module is moved to quarantine, it means that while we intend to keep it, it is currently broken or sufficiently untested that it can't be in the main IPython codebase. To be moved back into the main IPython codebase a module must: 1. Work fully. 2. Have a test suite. 3. Be a proper IPython extension and tie into the official APIs. 3. Have members of the IPython dev team who are willing to maintain it. When a module is moved to deathrow, it means that the code is either broken and not worth repairing, deprecated, replaced by newer functionality, or code that should be developed and maintained by a third party.

Moving clearcmd.py to quarantine. When a module is moved to quarantine, it means that while we intend to keep it, it is currently broken or sufficiently untested that it can't be in the main IPython codebase. To be moved back into the main IPython codebase a module must: 1. Work fully. 2. Have a test suite as much as possible. 3. Have members of the IPython dev team who are willing to maintain it.