<html>
<head>
<style>
body {
font-family: Verdana, sans-serif;
font-size: 0.8em;
color:#484848;
}
h1, h2, h3 { font-family: "Trebuchet MS", Verdana, sans-serif; margin: 0px; }
h1 { font-size: 1.2em; }
h2, h3 { font-size: 1.1em; }
a, a:link, a:visited { color: #2A5685;}
a:hover, a:active { color: #c61a1a; }
a.wiki-anchor { display: none; }
fieldset.attachments {border-width: 1px 0 0 0;}
hr {
width: 100%;
height: 1px;
background: #ccc;
border: 0;
}
span.footer {
font-size: 0.8em;
font-style: italic;
}
</style>
</head>
<body>
Issue #3219 has been updated by Peter Cock.
<ul>
<li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li>
<li><strong>% Done</strong> changed from <i>20</i> to <i>100</i></li>
</ul>
<p>Replaced by <a class="external" href="https://github.com/biopython/biopython/issues/906">https://github.com/biopython/biopython/issues/906</a> and <a class="external" href="https://github.com/biopython/biopython/issues/907">https://github.com/biopython/biopython/issues/907</a></p>
<hr />
<h1><a href="https://redmine.open-bio.org/issues/3219#change-15323">Feature #3219: Port Biopython documentation to Sphinx</a></h1>
<ul><li>Author: Eric Talevich</li>
<li>Status: Resolved</li>
<li>Priority: Low</li>
<li>Assignee: Biopython Dev Mailing List</li>
<li>Category: Documentation</li>
<li>Target version: </li>
<li>URL: </li></ul>
<p>Currently we use Epydoc for the API reference documentation, and LaTeX (to PDF via pdflatex, and HTML via hevea) for the tutorial. There's some material on the wiki to consider, too.</p>
<p>A number of Python projects, including CPython, now use Sphinx for documentation. Content is written in reStructuredText format, and can be pulled from both standalone .rst files and Python docstrings.</p>
<p>This offers several advantages: (i) API documentation will be prettier and easier to navigate; (ii) the Tutorial will be easier to edit for those not fluent in LaTeX; (iii) Since the API reference and Tutorial will be written in the same markup, potentially even pulling from some shared sources, it will be easier to address redundant or overlapping portions between the two, avoiding inconsistencies.</p>
<p>See:<br /><a class="external" href="http://sphinx.pocoo.org/">http://sphinx.pocoo.org/</a><br /><a class="external" href="http://docutils.sourceforge.net/">http://docutils.sourceforge.net/</a></p>
<p>Mailing list discussion:<br /><a class="external" href="http://lists.open-bio.org/pipermail/biopython-dev/2010-July/007977.html">http://lists.open-bio.org/pipermail/biopython-dev/2010-July/007977.html</a></p>
<p>Numpy's approach:<br /><a class="external" href="http://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt">http://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt</a></p>
<hr />
<span class="footer"><p>You have received this notification because you have either subscribed to it, or are involved in it.<br />To change your notification preferences, please click here and login: <a class="external" href="http://redmine.open-bio.org">http://redmine.open-bio.org</a></p></span>
</body>
</html>