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

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

Don't unregister failing post-exec callbacks automatically...
Don't unregister failing post-exec callbacks automatically Instead, print a message regarding the failure, pointing to new `disable_failing_post_execute` trait for skipping failing callbacks. When this flag is False (the default), failing callbacks will continue to be called. When True, behavior is unchanged from previous, where callbacks are only allowed to fail once.
Fernando Perez - - Load All Authors

File last commit:

r1334:049617d6
r5734:f972ef86
Show More
test_example.txt
24 lines | 728 B | text/plain | TextLexer
/ IPython / testing / plugin / test_example.txt
History | Annotation | Raw |Copy content |Copy permalink
=====================================
Tests in example form - pure python
=====================================
This file contains doctest examples embedded as code blocks, using normal
Python prompts. See the accompanying file for similar examples using IPython
prompts (you can't mix both types within one file). The following will be run
as a test::
>>> 1+1
2
>>> print "hello"
hello
More than one example works::
>>> s="Hello World"
>>> s.upper()
'HELLO WORLD'
but you should note that the *entire* test file is considered to be a single
test. Individual code blocks that fail are printed separately as ``example
failures``, but the whole file is still counted and reported as one test.