title: Are there any real alternatives to reStructuredText for Python documentation?
body: <p>I'm starting an open source Python project shortly and I'm trying to decide in advance how to write my docstrings. The obvious answer would be using reStructuredText and Sphinx with <code>autodoc</code>, because I <em>really</em> like the idea of simply properly documenting my code in my docstrings then have Sphinx automatically construct an API doc for me.</p>
  
  <p>The problem is the reStructuredText syntax it uses - I think it's completely unreadable before it's rendered. For instance:</p>
  
  <pre><code>:param path: The path of the file to wrap
  :type path: str
  :param field_storage: The :class:`FileStorage` instance to wrap
  :type field_storage: FileStorage
  :param temporary: Whether or not to delete the file when the File instance
      is destructed
  :type temporary: bool
  </code></pre>
  
  <p>You have to <em>really</em> slow down and take a minute to make any sense out of that syntactic jumble. I like much more the Google way (<a href="http://google-styleguide.googlecode.com/svn/trunk/pyguide.html" rel="nofollow noreferrer">Google Python Style Guide</a>), which counterpart to the above looks like this:</p>
  
  <pre>
  Args:
      path (str): The path of the file to wrap
      field_storage (FileStorage): The FileStorage instance to wrap
      temporary (bool): Whether or not to delete the file when the File
          instance is destructed
  </pre>
  
  <p><strong>Way</strong> nicer! But of course, Sphinx will have none of that and renders all the text after <code>Args:</code> in one long line.</p>
  
  <p>So to summarize - before I go and defile my code base with this reStructuredText syntax I would like to know if there are any real alternatives to using it and Sphinx, short of just writing my own API doc. For instance, is there an extension for Sphinx that handles Google Style Guide's docstring style?</p>