File: README.rst

package info (click to toggle)
python-biopython 1.78%2Bdfsg-4
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 65,756 kB
  • sloc: python: 221,141; xml: 178,777; ansic: 13,369; sql: 1,208; makefile: 131; sh: 70
file content (68 lines) | stat: -rw-r--r-- 1,794 bytes parent folder | download
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
Contributing to the Biopython Tutorial
======================================

Installing the tools you need
-----------------------------

On Ubuntu, you can install these with the following commands::

    sudo apt install hevea texlive-latex-base texlive-latex-extra python-pygments

Formatting code examples
------------------------

Code examples should be formatted using minted. Also, the Biopython tutorial
uses its own system for testing code examples, which is located in
``test_Tutorial.py``. You can read more about this system in the testing
chapter of the Biopython Tutorial.

Here is an example of Python code that uses the console to show output::

    %doctest path-to-folder
    \begin{minted}{pycon}
    >>> from Bio import SeqIO
    \end{minted}

These examples should use %doctest to verify that the output is correct.

Here is an example of Python code that does not show output::

    \begin{minted}{python}
    from Bio import SeqIO
    \end{minted}


Formatting text
---------------

Format headings as follows:

Chapter titles::

    \chapter{Title of Chapter}
    \label{chapter:chapterlabel}

Section titles::

    \section{Title of Section}
    \label{sec:sectionlabel}

Subsection titles::

    \subsection{Title of Subsection}

When referring to code in the middle of a paragraph, format it as follows::

    \verb|variable_name|

This will render ``variable_name`` in a monospace font. Within the pipe
characters, underscores will be interpreted literally, so they do not need
to be escaped.

Building the documentation
--------------------------

Build the documentation by running "make" in the Docs folder.

Once the documentation has been generated, you can inspect either Tutorial.pdf
or Tutorial.html in the Docs directory to see if the output is correct.