Python Pep8 Skill

• 4 spaces per level. No tabs. Ever.
• Continuation lines align with the opening delimiter or use a hanging indent with 4 extra spaces:

# Aligned with opening delimiter
result = some_function(first_argument, second_argument,
                       third_argument, fourth_argument)

# Hanging indent — preferred for long signatures
result = some_function(
    first_argument,
    second_argument,
    third_argument,
    fourth_argument,
)

• Always use trailing commas in multi-line collections, function arguments, and function parameters. This produces cleaner diffs:

# Good — trailing comma
config = {
    "host": "localhost",
    "port": 5432,
    "database": "myapp",
}

# Bad — no trailing comma
config = {
    "host": "localhost",
    "port": 5432,
    "database": "myapp"
}

Blank Lines

• 2 blank lines before and after top-level definitions (functions, classes).
• 1 blank line between methods inside a class.
• 1 blank line to separate logical sections within a function (sparingly).
• No blank line after a function's docstring.
• No blank line after if, for, while, with, try headers.
• No trailing blank lines at the end of a file. End with exactly one newline.

Whitespace

Spaces around operators:

# Good
x = 1
y = x + 2
result = value * (base + offset)
is_valid = name != "" and age >= 18

# Bad
x=1
y = x +2
result = value *( base + offset)

No spaces inside brackets:

# Good
items[0]
data["key"]
func(arg1, arg2)

# Bad
items[ 0 ]
data[ "key" ]
func( arg1, arg2 )

No spaces around = in keyword arguments or default values:

# Good
def connect(host="localhost", port=5432, timeout=30):
    client.send(data=payload, retry=True)

# Bad
def connect(host = "localhost", port = 5432, timeout = 30):
    client.send(data = payload, retry = True)

Spaces around = in annotated assignments:

# Good — space around = when annotation is present