##// END OF EJS Templates
Backport PR #2214: use KernelApp.exec_lines/files in IPEngineApp...
Backport PR #2214: use KernelApp.exec_lines/files in IPEngineApp This change means that all your startup/exec_lines config is inherited by engines. should be backported for 0.13.1, because engine startup code is impossible to configure in 0.13. The real long-term fix for this is to make IPEngineApp a subclass of IPKernelApp, but this should be an adequate band-aid until then. closes #2213

File last commit:

r1334:049617d6
r8079:b1241d50
Show More
test_exampleip.txt
30 lines | 816 B | text/plain | TextLexer
=================================
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