blob: a764a372ac198e404009e8ca8144021f112817a4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
Typographical Conventions
=========================
Literals, filenames and function arguments are presented using the
following style:
``argument1``
Warnings, which represent limitations and need-to-know information
related to a topic or concept are presented in the following style:
.. warning::
This is a warning.
Notes, which represent additional information related to a topic or
concept are presented in the following style:
.. note::
This is a note.
We present Python method names using the following style:
:meth:`Python.method_name`
We present Python class names, module names, attributes and global
variables using the following style:
:class:`Python.class_module_or_attribute.name`
References to glossary terms are presented using the following style:
:term:`Pylons`
URLs are presented using the following style:
`Pylons <http://pylonshq.com>`_
References to sections and chapters are presented using the following
style:
:ref:`traversal_chapter`
Python code blocks are presented in the following style:
.. code-block:: python
:linenos:
def foo(abc):
pass
Blocks of XML markup are presented in the following style:
.. code-block:: xml
:linenos:
<root>
<!-- ... more XML .. -->
</root>
When a command that should be typed on one line is too long to fit on
a page, the backslash ``\`` is used to indicate that the following
printed line should actually be part of the command:
.. code-block:: text
c:\bigfntut\tutorial> ..\Scripts\nosetests --cover-package=tutorial \
--cover-erase --with-coverage
A sidebar, which presents a concept tangentially related to content
discussed on a page, is rendered like so:
.. sidebar:: This is a sidebar
Sidebar information.
|
