I've written a follow-up  on why the CSV standard library is
broken, broken, broken. Let's have a look at the wonders of CSV
formats / dialects
such as MYSQL CSV export or PostgreSQL CSV or TEXT export.
In a nutshell - the standard CSV parser is a (simplistic) kludge
using string.split() and, thus, needs to get replaced with a "real" parser
that can handle more "edge" cases / formats.
Questions and comments welcome.
Also if want to see other CSV formats pre-configured and supported
"out-of-the-box" in the new csv reader, let us know.
PS: Did you miss the first part (part I in the series)? See 
(Part II - Follow-up)