PEP 8 Style Guide for Python Code

If you don’t know what that is, well…you should probably start by reading this article because we’re not going to hold your hand through every single line of it.
First: why should you care about PEP 8? Well, let me tell ya consistency is key when it comes to code. And by following the guidelines laid out in this style guide, you can ensure that your Python code looks and feels like everyone else’s (which is a good thing). Plus, it makes it easier for other people to read and understand what you wrote without having to decipher some crazy-looking syntax or variable names.
Now, Let’s jump right into the details of PEP 8. First off, use spaces instead of tabs (because who wants to deal with those ***** tab characters anyway?). And make sure your indentation is consistent four spaces are a good compromise between small and large indentations.
Next up: line length. Keep it under 79 characters so that users with smaller displays can still see everything without having to scroll left and right like crazy people. And if you need to break up a long line of code, use blank lines to separate functions or classes (because who wants to read through one giant block of text anyway?).
Speaking of comments put them on their own line so that they’re easy to spot and don’t get lost in the sea of code. And if you want to add some extra context, use docstrings (which are basically just fancy comments with a little bit more structure) to explain what your function or class does.
Finally, when it comes to operators and commas, put spaces around them so that they’re easier to read and understand. But don’t go overboard too many spaces can make your code look cluttered and messy (which is the opposite of what we want!).
And if you’re still not convinced, just remember: consistency is key when it comes to code (and who wants to deal with inconsistent code anyway?).

SICORPS