Documentation is hugely important, not just to communicate to other people what is the goal of a function/class/method/module, but also to yourself.
When you’ll come back to your code 6 or 12 months from now, you might not remember all the knowledge you are holding in your head, and reading your code and understanding what it is supposed to do, will be much more difficult.
Comments are one way to do so:
# this is a comment num = 1 #this is another comment
Another way is to use docstrings.
The utility of docstrings is that they follow conventions and as such they can be processed automatically.
This is how you define a docstring for a function:
def increment(n): """Increment a number""" return n + 1
This is how you define a docstring for a class and a method:
class Dog: """A class representing a dog""" def __init__(self, name, age): """Initialize a new dog""" self.name = name self.age = age def bark(self): """Let the dog bark""" print('WOF!')
Document a module by placing a docstring at the top of the file, for example supposing this is
"""Dog module This module does ... bla bla bla and provides the following classes: - Dog ... """ class Dog: """A class representing a dog""" def __init__(self, name, age): """Initialize a new dog""" self.name = name self.age = age def bark(self): """Let the dog bark""" print('WOF!')
Docstrings can span over multiple lines:
def increment(n): """Increment a number """ return n + 1
Python will process those and you can use the
help() global function to get the documentation for a class/method/function/module.
For example calling
help(increment) will give you this:
Help on function increment in module __main__: increment(n) Increment a number
There are many different standards to format docstrings, and you can choose to adhere to your favorite one.
I like Google’s standard: https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
Standard allows to have tools to extract docstrings and automatically generate documentation for your code.