Build the first working label file cleaner

Build only what the claim requires: UTF-8 lines become lowercase, de-duplicated labels in a new file; source untouched. Prefer boring, deterministic code over frameworks you cannot yet explain. Run the path twice; identical output on this fixture is a feature, not a lack of creativity.

from pathlib import Path
Path('labels.txt').write_text('YES\nyes\n\nNo\n', encoding='utf-8')
raw=[ln.strip().lower() for ln in Path('labels.txt').read_text(encoding='utf-8').splitlines() if ln.strip()]
clean=list(dict.fromkeys(raw))
Path('clean-labels.txt').write_text('\n'.join(clean)+'\n', encoding='utf-8')
print(clean)

Expected evidence: ('yes', 'no'). Read each printed intermediate as part of the argument that the path works—not as decoration.

Narrate the journey from raw input to result for a single example from labels.txt with YES/yes/No/blank lines. If you cannot name an intermediate, the implementation is still too opaque for this lab. Only after this path is solid should you generalize data sources or UI.

While implementing the label file cleaner, print or log at least three intermediates that map to the claim (UTF-8 lines become lowercase, de-duplicated labels in a new file; source untouched). Good intermediates are values a teammate could recompute with a calculator or diff. Bad intermediates are framework traces you cannot explain.

Re-run with labels.txt with YES/yes/No/blank lines twice. If the second run differs, either the path is nondeterministic (document the seed) or you have hidden global state—both are lab bugs until named.

Stop adding features once the path supports normalize noisy training labels without destroying the source file. Extra UI, extra tools, or extra models belong in later chapters. The mastery bar for this page is simply: a deterministic end-to-end path with intermediates.

At the implementation stage for python-file-handling, the job is narrower than finishing a product demo. You are creating one progressive evidence piece about labels.txt with YES/yes/No/blank lines that later pages inherit without redefining success. Keep that fixture small enough to inspect by hand, keep outputs copy-pasteable as text, and refuse to narrate this baseline as if it were a production SLA: manual unique-lower count of the fixture before coding.

For this page specifically, success looks like a deterministic path with printed intermediates while still centering the user decision to normalize noisy training labels without destroying the source file. If you cannot point to a file, command, or assertion that proves that for the label file cleaner, stay on this page instead of advancing.

ML Python starter

Previous · Next