Two small output issues seen across verbs:
- Duplicate log lines. Every verb prints its completion message twice, in two formats, e.g.
... layup.convert ... INFO - Data has been written to X.csv and INFO:layup.convert:Data has been written to X.csv.
This is consistent with a custom handler plus propagation to the root logger.
- Header read twice.
convert logs Reading the first line ... as header twice per run (~5 ms apart, same format), suggesting the reader opens/peeks the input file twice.
Both are cosmetic, but they make the CLI look chatty, and the double read may waste I/O on large inputs.
Suggested fix: set logger.propagate = False (or configure a single handler), and peek the header once.
Found during a clean-room, fresh-user install + test run-through (fresh venv + --recursive clone, following the README Quickstart), 2026-07-10.
Two small output issues seen across verbs:
... layup.convert ... INFO - Data has been written to X.csvandINFO:layup.convert:Data has been written to X.csv.This is consistent with a custom handler plus propagation to the root logger.
convertlogsReading the first line ... as headertwice per run (~5 ms apart, same format), suggesting the reader opens/peeks the input file twice.Both are cosmetic, but they make the CLI look chatty, and the double read may waste I/O on large inputs.
Suggested fix: set
logger.propagate = False(or configure a single handler), and peek the header once.Found during a clean-room, fresh-user install + test run-through (fresh venv +
--recursiveclone, following the README Quickstart), 2026-07-10.