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

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

Refactor of coloring and traceback mechanism....
Refactor of coloring and traceback mechanism. This should not change behavior be should slightly clean the code to be a bit more pythonic, and start to introduce methods that avoid side effect (that is to say return values instead of directly writing to stdout). I keep it relatively small and simple for now. My goal is to slowly change the traceback mechanisme to separate buiding the data structure from rendering it to potentially introduce richer tracebacks. Locally I've also started from the other side (re build a traceback rendered from scratch) to see what's needed.
MinRK - - Load All Authors

File last commit:

r7777:2255c2b8
r24334:50b3e0b7
Show More
test_example.txt
24 lines | 730 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.