Testing the new theme:
Some stuff here!
What about some inline stuff? Cool.
With success comes the temptation to tell oneself a story, to round off the edges, to cut out your lucky breaks and add a certain mythology to it all. You know, that arcing narrative of Herculean struggle for greatness against all odds: sleeping on the floor, being disowned by my parents, suffering for my ambition. It’s a type of storytelling in which eventually your talent becomes your identity and your accomplishments become your worth.
But a story like this is never honest or helpful. In my retelling to you just now, I left a lot out. Conveniently omitted were the stresses and temptations; the stomach-turning drops and the mistakes—all the mistakes—were left on the cutting-room floor in favor of the highlight reel. They are the times I would rather not discuss: A public evisceration by someone I looked up to, which so crushed me at the time that I was later taken to the emergency room. The day I lost my nerve, walked into my boss’s office, and told him I couldn’t cut it and was going back to school—and meant it. The ephemeral nature of best-sellerdom, and how short it actually was (a week). The book signing that one person showed up at. The company I founded tearing itself to pieces and having to rebuild it. Twice. These are just some of the moments that get nicely edited out.
Blah blah blah.
Table of Contents
- 1 Structural Elements
2 Body Elements
- 2.1 Paragraphs
- 2.2 Bullet Lists
- 2.3 Enumerated Lists
- 2.4 Definition Lists
- 2.5 Field Lists
- 2.6 Option Lists
- 2.7 Literal Blocks
- 2.8 Line Blocks
- 2.9 Block Quotes
- 2.10 Doctest Blocks
- 2.11 Tables
- 2.12 Footnotes
- 2.13 Citations
- 2.14 Targets
- 2.15 Directives
- 2.16 Substitution Definitions
- 2.17 Comments
- 3 Error Handling
That's it, the text just above this line.
Here's a transition:
It divides the section.
Paragraphs contain text and may contain inline markup: emphasis, strong emphasis, inline literals, standalone hyperlinks (http://www.python.org), external hyperlinks (Python ), internal cross-references (example), external hyperlinks with embedded URIs (Python web site), footnote references (manually numbered , anonymous auto-numbered , labeled auto-numbered , or symbolic [*]), citation references ([CIT2002]), substitution references (), and (see Targets below for a reference back to here). Character-level inline markup is also possible (although exceedingly ugly!) in reStructuredText.
The default role for interpreted text is Title Reference. Here are some explicit interpreted text roles: a PEP reference (PEP 287); an RFC reference (RFC 2822); a subscript; a superscript; and explicit roles for standard inline markup.
Let's test wrapping and whitespace significance in inline literals: This is an example of --inline-literal --text, --including some-- strangely--hyphenated-words. Adjust-the-width-of-your-browser-window to see how the text is wrapped. -- ---- -------- Now note the spacing between the words of this sentence (words should be grouped in pairs).
If the --pep-references option was supplied, there should be a live link to PEP 258 here.
A bullet list
- Nested bullet list.
- Nested item 2.
Paragraph 2 of item 2.
- Nested bullet list.
- Nested item 2.
- Third level.
- Item 2.
- Nested item 3.
- lower alpha)
- (lower roman)
- upper alpha.
- upper roman)
- upper alpha.
- (lower roman)
- lower alpha)
Lists that don't start at 1:
List items may also be auto-enumerated.
- Term : classifier
Definition paragraph 1.
Definition paragraph 2.
Field lists map field names to field bodies, like database records. They are often part of an extension syntax. They are an unambiguous variant of RFC 2822 fields.
|how arg1 arg2:||
The field marker is a colon, the field name, and a colon.
The field body may contain one or more body elements, indented relative to the field marker.
For listing command-line options:
|-a||command-line option "a"|
|-b file||options can have arguments and long descriptions|
|--long||options can be long also|
|--input=file||long options can also have arguments|
The description can also start on the next line.
The description may contain multiple body elements, regardless of where it starts.
|-x, -y, -z||Multiple options are an "option group".|
|-v, --verbose||Commonly-seen: short & long options.|
|-1 file, --one=file, --two file|
|Multiple options with arguments.|
|/V||DOS/VMS-style options too|
There must be at least two spaces between the option and the description.
Literal blocks are indicated with a double-colon ("::") at the end of the preceding paragraph (over there -->). They can be indented:
if literal_block: text = 'is left as-is' spaces_and_linebreaks = 'are preserved' markup_processing = None
Or they can be quoted without indentation:
>> Great idea! > > Why didn't I think of that?
Take it away, Eric the Orchestra Leader!
A one, two, a one two three fourHalf a bee, philosophically,must, ipso facto, half not be.But half the bee has got to be,vis a vis its entity. D'you see?But can a bee be said to beor not to be an entire bee,when half the bee is not a bee,due to some ancient injury?Singing...
Block quotes consist of indented body elements:
My theory by A. Elk. Brackets Miss, brackets. This theory goes as follows and begins now. All brontosauruses are thin at one end, much much thicker in the middle and then thin again at the far end. That is my theory, it is mine, and belongs to me and I own it, and what it is too.
—Anne Elk (Miss)
>>> print 'Python-specific usage examples; begun with ">>>"' Python-specific usage examples; begun with ">>>" >>> print '(cut and pasted from interactive Python sessions)' (cut and pasted from interactive Python sessions)
Here's a grid table followed by a simple table:
|Header row, column 1 (header rows optional)||Header 2||Header 3||Header 4|
|body row 1, column 1||column 2||column 3||column 4|
|body row 2||Cells may span columns.|
|body row 3||Cells may span rows.||
|body row 4|
|body row 5||Cells may also be empty: -->|
|A||B||A or B|
A footnote contains body elements, consistently indented by at least 3 spaces.
This is the footnote's second paragraph.
|||(1, 2) Footnotes may be numbered, either manually (as in ) or automatically using a "#"-prefixed label. This footnote has a label so it can be referred to from multiple places, both as a footnote reference () and as a hyperlink reference (label).|
|||This footnote is numbered automatically and anonymously using a label of "#" only.|
|[*]||Footnotes may also use symbols, specified with a "*" label. Here's a reference to the next footnote: [†].|
|[†]||This footnote shows the next symbol in the sequence.|
|||Here's an unreferenced footnote|
|[CIT2002]||(1, 2) Citations are text-labeled footnotes. They may be rendered separately and differently from footnotes.|
Here's a reference to the above, [CIT2002].
Duplicate names in section headers or other implicit targets will generate "info" (level-1) system messages. Duplicate names in explicit targets will generate "warning" (level-2) system messages.
Since there are two "Duplicate Target Names" section headers, we cannot uniquely refer to either of them by name.
These are just a sample of the many reStructuredText Directives. For others, please see http://docutils.sourceforge.net/docs/ref/rst/directives.html.
An image directive (also clickable -- a hyperlink reference):
A figure directive:
|re||Revised, revisited, based on 're' module.|
|Structured||Structure-enhanced text, structuredtext.|
|Text||Well it is, isn't it?|
This paragraph is also part of the legend.
Directives at large.
Don't take any wooden nickels.
Mad scientist at work!
Does not compute.
It's bigger than a bread box.
- Wash behind your ears.
- Clean up your room.
- Call your mother.
- Back up your data.
This is a note.
15% if the service is good.
Strong prose may provoke extreme mental exertion. Reader discretion is strongly advised.
And, by the way...
You can make up your own admonition too.
This paragraph contains a literal block:
Connecting... OK Transmitting data... OK Disconnecting... OK
and thus consists of a simple paragraph, a literal block, and another simple paragraph. Nonetheless it is semantically one paragraph.
This construct is called a compound paragraph and can be produced with the "compound" directive.
An inline image () example:
(Substitution definitions are not visible in the HTML source.)
Any errors caught during processing will generate system messages.
There should be six messages in the following, auto-generated section, "Docutils System Messages":