Created
November 6, 2018 06:11
-
-
Save andreajparker/af58bdae2090647588f7c438c07f46c2 to your computer and use it in GitHub Desktop.
Google-style docstring for Python
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# -*- coding: utf-8 -*- | |
"""Example Google style docstrings. | |
This module demonstrates documentation as specified by the `Google Python | |
Style Guide`_. Docstrings may extend over multiple lines. Sections are created | |
with a section header and a colon followed by a block of indented text. | |
Example: | |
Examples can be given using either the ``Example`` or ``Examples`` | |
sections. Sections support any reStructuredText formatting, including | |
literal blocks:: | |
$ python example_google.py | |
Section breaks are created by resuming unindented text. Section breaks | |
are also implicitly created anytime a new section starts. | |
Attributes: | |
module_level_variable1 (int): Module level variables may be documented in | |
either the ``Attributes`` section of the module docstring, or in an | |
inline docstring immediately following the variable. | |
Either form is acceptable, but the two should not be mixed. Choose | |
one convention to document module level variables and be consistent | |
with it. | |
Todo: | |
* For module TODOs | |
* You have to also use ``sphinx.ext.todo`` extension | |
.. _Google Python Style Guide: | |
http://google.github.io/styleguide/pyguide.html | |
""" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment