James Gray
6/9/2008 11:27:00 PM
On Jun 9, 2008, at 4:52 PM, Charles Walden wrote:
> My experience (at least a year ago) was that fastercsv was a great
> way to go if you had very clean files without errors, odd
> characters, etc. Unfortunately, I had files that were a bit more
> problematic and so I ended up using a combination of either parsing
> it myself (split, regexs. etc) and catching all the errors and
> handling them or using the parse_line method in the standard csv
> library.
FasterCSV has a parse_line() method as well, just FYI.
James Edward Gray II