Vaibhav Mallya <vaibhavmal...@gmail.com> added the comment: Hello R. David & Terry!
Appreciate your prompt responses. While experimenting with different test cases I realized that escaped slashes and newlines are intrinsically annoying to reason about as stringy-one-liners, so I threw together a small tarball test case - attached - to make sure we're on the same page. To be clear, I was referring *solely* to reading with csv.DictReader (we're not using the writing part). The assertion for the multi_line_csv_unquoted fails, and I believe it should succeed. I hadn't considered the design-bug vs code-bug angle. I also think that documenting this somehow - explicitly - would help others, since there's no mention of the interaction here, with what should be a fairly common use-case. It might even make sense to make a "strong recommendation" that everything is quoted + escaped (much as redshift makes a strong recommendation to escape). Our data pipeline is doing fine after the right parameters on both sides, this is more about improving Python for the rest of the community. Thanks for your help, I will of course respect any decision you make. ---------- Added file: https://bugs.python.org/file47181/csv_test.tar _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31590> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
