There might be different documentation strings available. You need not need to worry about the fact that you have to reinvent the wheel to study all. The formats of all the Documentation strings are nearly similar. The patterns are similar, but there are only nitty-gritty changes in each format.

Sphinx is the easy and traditional style, verbose and was initially created specifically for the Python Documentation. Sphinx uses a reStructuredText which is similar in usage to Markdown.

class Vehicle(object):

'''

def __init__(self, arg, *args, **kwargs):

self.arg = arg

def cars(self, distance, destination):

'''We can't travel a certain distance in vehicles without fuels, so here's the fuels

'''

pass

Google Style is easier and more intuitive to use. It can be used for the shorter form of documentation. A configuration of python file needs to be done to get started, so you need to add either sphinx.ext.napoleon or sphinxcontrib.napoleon to the extensions list in conf.py.

class Vehicles(object):

'''

def __init__(self, arg, *args, **kwargs):

self.arg = arg

def cars(self, distance,destination):

'''We can't travel distance in vehicles without fuels, so here is the fuels

pass

Numpy style has a lot of details in the documentation. It is more verbose than other documentation, but it is an excellent choice if you want to do detailed documentation, i.e., extensive documentation of all the functions and parameters.

class Vehicles(object):

'''

def __init__(self, arg, *args, **kwargs):

self.arg = arg

def cars(self, distance, destination):

'''We can't travel distance in vehicles without fuels, so here is the fuels

pass