This is a sample ReStructuredText document.
Contents
Here we have a numbered list
- Four
- Five
- Six
and a regular list
- One
- Two
- Three
and a definition list
- one
- The first number.
- two
- Also a number
- three
- You get the idea!
and finally a field list
| One: | is a field |
|---|---|
| Two: | is also a field |
Usage: restview [options] [files...]
| -h, --help | show help |
| --long-description | |
| extract and display the long_description field from setup.py | |
Here's some Python code:
def uniq(seq):
"""Drop duplicate elements from the sequence.
Does not preserve the order.
"""
return sorted(set(seq))
also with syntax highlighting:
def uniq(seq):
"""Drop duplicate elements from the sequence.
Does not preserve the order.
"""
return sorted(set(seq))oh and some doctests that demonstrate the uniq() function:
>>> uniq([1, 2, 3, 2, 1]) [1, 2, 3]>>> uniq([3, 2, 1]) [1, 2, 3]
The alignment is kept the same for all of them, including simple quoted blocks
Like this one.
Some very important [*] text.
| [*] | not really that important. |
| Truth | |||
| H0 | Ha | ||
| Judgement | H0 | Confidence 1-\alpha | Error \beta |
| Ha | Error \alpha | Power 1-\beta | |
Some text.
Some more text.
How can we live without demonstrating the :doc:`errors`?