##// END OF EJS Templates
Merge pull request #4515 from Carreau/load-speedup...
Merge pull request #4515 from Carreau/load-speedup Spring Cleaning, and Load speedup 0) prompt '*' strore fix + tab remove tooltip tab was not cancelling tooltip bringing to cases where you could have tooltip andcompleter open. Do not store '*' when serializing cells. get rid of most slowdown at notebook loading. 1) Do not setOption('mode',new_mode) on CM if new and old mode are the same. It triggert a lot of calculation of bounding box in the end. 2) Do not select cell when loading the notebook it triggers a lot of CM even that check visible things and so on and so forth. So add a option to add_cell_at_index not to select it 3) jQuery $.attr has some magics, but has a slight overhead on real native ELEM.setAttribute DOM method. Seem slight improvement when loads of PNGs on one page

File last commit:

r11729:5cc34183
r13580:af808396 merge
Show More
history.rst
34 lines | 1.4 KiB | text/x-rst | RstLexer

History

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.