String Parsing (split, fields, typed values)

Parsing turns raw text into typed data—splitting on delimiters, stripping noise, converting fields to numbers, and validating arity. Most bugs are wrong assumptions about spaces, empty tokens, or multiple separators.

Why this shows up in the real world

Config files map key=value lines into dicts. Sports feeds parse clock strings like 12:34 into minutes.

Core idea (explained for students)

Pipeline: line.strip() → parts = line.split(',') → int(parts[0]) inside try/except or explicit checks. Use partition when you only need the first =.

Try this in Python

def parse_kv(line: str) -> tuple[str, str]:
    k, _, v = line.partition("=")
    return k.strip(), v.strip()


print(parse_kv("  name = Ada Lovelace  "))

Common mistakes

• split() with no args splits on any whitespace—different from split(' ') which keeps empty runs.
• Leading zeros on numeric fields—decide int vs preserve string.

Key takeaways

• Write small parse helpers per record shape and unit-test them on odd lines.
• Prefer split(maxsplit=...) when the tail should stay intact.