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

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

promote aliases and flags, to ensure they have priority over config files...
promote aliases and flags, to ensure they have priority over config files add Application.flatten_flags() method, which adjusts the alias and flag dicts, such that they point to the subclass in the Application.classes list when passed to the argv parser. This prevents TerminalInteractiveShell.colors in a config file overriding `--colors` on the command-line, which points to InteractiveShell.colors. Flattening is only done when the answer is unambiguous, so multiply inherited classes (e.g. Launchers in ipcluster) are not touched. also remove now-obsolete manual workaround for this in IPClusterStart closes gh-849
Fernando Perez - - Load All Authors

File last commit:

r1334:049617d6
r4977:d2ab6923
Show More
test_exampleip.txt
30 lines | 816 B | text/plain | TextLexer
/ IPython / testing / plugin / test_exampleip.txt
History | Annotation | Raw |Copy content |Copy permalink
=================================
Tests in example form - IPython
=================================
You can write text files with examples that use IPython prompts (as long as you
use the nose ipython doctest plugin), but you can not mix and match prompt
styles in a single file. That is, you either use all ``>>>`` prompts or all
IPython-style prompts. Your test suite *can* have both types, you just need to
put each type of example in a separate. Using IPython prompts, you can paste
directly from your session::
In [5]: s="Hello World"
In [6]: s.upper()
Out[6]: 'HELLO WORLD'
Another example::
In [8]: 1+3
Out[8]: 4
Just like in IPython docstrings, you can use all IPython syntax and features::
In [9]: !echo "hello"
hello
In [10]: a='hi'
In [11]: !echo $a
hi