ReStructuredText should not be confused with Representational state transfer.
| reStructuredText | |
| Extension: | .rst |
| Mime: |
|
| Owner: | David Goodger |
| Latest Release Version: | Revision 8407 |
| Open: | Public domain |
reStructuredText (RST, ReST, or reST) is a file format for textual data used primarily in the Python programming language community for technical documentation.
It is part of the Docutils project of the Python Doc-SIG (Documentation Special Interest Group), aimed at creating a set of tools for Python similar to Javadoc for Java or Plain Old Documentation (POD) for Perl. Docutils can extract comments and information from Python programs, and format them into various forms of program documentation.[1]
In this sense, reStructuredText is a lightweight markup language designed to be both processable by documentation-processing software such as Docutils, and be easily readable by human programmers who are reading and writing Python source code.
reStructuredText evolved from an earlier lightweight markup language called StructuredText[2] (developed by Zope). There were a number of problems with StructuredText, and reST was developed to address them.[3] The name reStructuredText was chosen to indicate that reST is a "revised, reworked, and reinterpreted StructuredText."[4]
Parts of the reST syntax were inspired by the Setext language from the early 1990s. Elements of the common RFC822 Internet Message Format and Javadoc formats were also considered for inclusion in the design.[5]
reStructuredText was first released in June 2001.[6] It began to see significant use in the Python community in 2002.[7]
The reference implementation of the reST parser is a component of the Docutils text processing framework in the Python programming language, but other parsers are available.
The Docutils project has not registered any MIME type for reStructuredText nor designated any unregistered MIME type as official, but documents the MIME type text/x-rst as in de facto use by, for example, the build system for the Python website.[8] The same MIME type is used in the freedesktop.org file type database used by desktop environments on Linux.[9] Another MIME type,, was registered as a vanity MIME type by a third party in 2003 to represent reStructuredText, and remains the only IANA-registered MIME type for reStructuredText,[10] although it is not acknowledged as such by the Docutils project.[8]
reStructuredText is commonly used for technical documentation, for example, in documentation of Python libraries.[11] However, it is suitable for a wide range of texts.
Since 2008, reST has been a core component of Python's Sphinx document generation system.
Trac also supports reStructuredText,[12] as do GitHub and Bitbucket.
In 2011, Distributed Proofreaders, which prepared texts for Project Gutenberg, was considering adoption of reST as a basic format from which other ebook formats could be generated.[13]
In July 2016 the Linux kernel project decided to transition from DocBook based documentation to reStructuredText and the Sphinx toolchain.[14] [15]
The software build tool CMake switched from a custom markup language to reStructuredText in version 3.0 for its documentation.[16]
| Text using rST syntax | Corresponding HTML produced by an rST processor | Text viewed in a browser | ||||
|---|---|---|---|---|---|---|
=Document Heading= Heading Sub-heading----------- Paragraphs are separated by a blank line. | Document HeadingHeadingSub-headingParagraphs are separatedby a blank line. | Document Heading Heading Sub-heading Paragraphs are separatedby a blank line. | ||||
Horizontal rule: ---- | Text attributes emphasis,strong emphasis, Horizontal rule: | Text attributes emphasis,strong emphasis, monospace.Horizontal rule: | ||||
Numbered list: 1. lather2. rinse3. repeat Nested lists: 1. fruits * apple * banana 2. vegetables * carrot * broccoli | Bullet list:
Numbered list:
Nested lists:
| Bullet list:
Numbered list:
Nested lists:
| ||||
.. image:: Icon-pictures.png :alt: Image If text is indented, it is treated as a block quotation: Should array indices start at 0 or 1? My suggested compromise of 0.5 was rejected without, I thought, proper consideration. -- Stan Kelly-Bootle reST uses :: at the end of the paragraph prior to a pre-formatted code block:: Y = lambda f: (lambda x: f(x(x)))(lambda x: f(x(x))) | Multi-line text can | span in tables | with a pipe character. | An example.
If text is indented, it is treated as a block quotation, and the final attribution line is handled automatically: Should array indices start at 0 or 1?My suggested compromise of 0.5 was rejected without, I thought, proper consideration.-- Stan Kelly-Bootle reST uses :: at the end of the paragraph prior to a pre-formatted code block: class="literal-block"> Y = lambda f: (lambda x: f(x(x)))(lambda x: f(x(x))) Multi-line text can | An example. If text is indented, it is treated as a block quotation, and the final attribution line is handled automatically: Should array indices start at 0 or 1?My suggested compromise of 0.5 was rejected without, I thought, proper consideration.-- Stan Kelly-Bootle reST uses :: at the end of the paragraph prior to a pre-formatted code block: class="literal-block"> Y = lambda f: (lambda x: f(x(x)))(lambda x: f(x(x))) Multi-line text can |
