you need to keep few details in mind when you're styling functions functions should have descriptive namesand these names should use lowercase letters and underscores descriptive names help you and others understand what your code is trying to do module names should use these conventions as well every function should have comment that explains concisely what the function does this comment should appear immediately after the function definition and use the docstring format in well-documented functionother programmers can use the function by reading only the description in the docstring they should be able to trust that the code works as describedand as long as they know the name of the functionthe arguments it needsand the kind of value it returnsthey should be able to use it in their programs if you specify default value for parameterno spaces should be used on either side of the equal signdef function_name(parameter_ parameter_ ='default value'the same convention should be used for keyword arguments in function callsfunction_name(value_ parameter_ ='value'pep (you limit lines of code to characters so every line is visible in reasonably sized editor window if set of parameters causes function' definition to be longer than characterspress enter after the opening parenthesis on the definition line on the next linepress tab twice to separate the list of arguments from the body of the functionwhich will only be indented one level most editors automatically line up any additional lines of parameters to match the indentation you have established on the first linedef function_nameparameter_ parameter_ parameter_ parameter_ parameter_ parameter_ )function body if your program or module has more than one functionyou can separate each by two blank lines to make it easier to see where one function ends and the next one begins all import statements should be written at the beginning of file the only exception is if you use comments at the beginning of your file to describe the overall program