##// END OF EJS Templates
Fix exception color problems in win32....
Fix exception color problems in win32. In all the recent work to have the test suite play nice with doctest of full ipython sessions, I inadvertedly started sending exceptions directly to sys.stderr. On windows we MUST go via Term.cerr, which uses pyreadline to handle color escapes, while sys.stderr just shows garbage on screen. As of this revision, the test suite passes fully on win32 and linux, and interactive use also seems OK on all fronts. We're getting closer to RC status...

File last commit:

r2276:cdecc6d2
r2459:e687d797
Show More
history.txt
34 lines | 1.4 KiB | text/plain | TextLexer
.. _history:
=======
History
=======
Origins
=======
IPython was starting in 2001 by Fernando Perez while he was a graduate student
at the University of Colorado, Boulder. IPython as we know it today grew out
of the following three projects:
* ipython by Fernando PĂ©rez. Fernando began using Python and ipython began as
an outgrowth of his desire for things like Mathematica-style prompts, access
to previous output (again like Mathematica's % syntax) and a flexible
configuration system (something better than :envvar:`PYTHONSTARTUP`).
* IPP by Janko Hauser. Very well organized, great usability. Had
an old help system. IPP was used as the "container" code into
which Fernando added the functionality from ipython and LazyPython.
* LazyPython by Nathan Gray. Simple but very powerful. The quick
syntax (auto parens, auto quotes) and verbose/colored tracebacks
were all taken from here.
Here is how Fernando describes the early history of IPython:
When I found out about IPP and LazyPython I tried to join all three
into a unified system. I thought this could provide a very nice
working environment, both for regular programming and scientific
computing: shell-like features, IDL/Matlab numerics, Mathematica-type
prompt history and great object introspection and help facilities. I
think it worked reasonably well, though it was a lot more work than I
had initially planned.