{"id":225,"date":"2019-12-26T23:15:00","date_gmt":"2019-12-26T23:15:00","guid":{"rendered":"https:\/\/zofxare.com\/zofxare\/blog\/2019\/12\/26\/python-tutorial-series-style-guide\/"},"modified":"2019-12-26T23:15:00","modified_gmt":"2019-12-26T23:15:00","slug":"python-tutorial-series-style-guide","status":"publish","type":"post","link":"https:\/\/zofxare.com\/zofxare\/blog\/2019\/12\/26\/python-tutorial-series-style-guide\/","title":{"rendered":"Python Tutorial Series – Style Guide"},"content":{"rendered":"

A best practice in programming is to adhere to a consistent style guide. It allows for more readable code and easier maintenance. Python actually has it’s own suggested style guide. It is online at: https:\/\/www.python.org\/dev\/peps\/pep-0008\/<\/a>.
\nSome highlights include:<\/p>\n

– Indentation is 4 spaces – This is really important. If a file has a line with incorrect indentation, an error will be thrown when running the file.
\n– Add a line break before binary operators.
\n– Imports should be on separate lines.
\n– Pick either single quotes or double quotes and stick with it.
\n– Surround binary operators with a space on each side.
\n– Avoid spaces inside braces, brackets and parentheses.
\n– Avoid trailing whitespace.
\n– Modules should have short, all lowercase names, separated by underscores for multi-word names.
\n– Class names and type variable names should have each word start with a capital letter, ex: ClassName.
\n– Function and variable names should be all lowercase with each word separated by an underscore, ex: my_function.
\n– Constants should be all capitalized with each word separated by an underscore, ex: THREE = “three”.<\/p>\n