Original Summary

I put together a small, dependency-free Python repo to test one deceptively simple CSV failure. A blank row crashes the original parser; the repaired parser skips only truly blank rows and still raises on invalid non-empty rows. The repo includes both versions and three tests: original failure, repaired behavior, and the malformed-data boundary. Run python -m unittest -v test_csv_repair.py to see them. It is a self-produced demo with synthetic input, not a client case. Project: https://github.com/ohyoseok92/python-csv-repair-demo I am looking for feedback on the boundary: for a small import script, would you fail fast on malformed non-empty rows as this demo does, or collect them in a separate exceptions report? What would make the repair easier to review?   submitted by   /u/CutDry6295 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/12 19:19:49