diff options
| author | Skip Montanaro <skip@pobox.com> | 2006-07-29 20:06:05 (GMT) |
|---|---|---|
| committer | Skip Montanaro <skip@pobox.com> | 2006-07-29 20:06:05 (GMT) |
| commit | abd51a358561b52d4d9ddc75b82b9749a3aba55a (patch) | |
| tree | 79083050eeca71cfd1e5c5dcb91c43e82e5f2b19 | |
| parent | 45540b0922f1858c4214287941b9c3b2888767e0 (diff) | |
| download | cpython-abd51a358561b52d4d9ddc75b82b9749a3aba55a.zip cpython-abd51a358561b52d4d9ddc75b82b9749a3aba55a.tar.gz cpython-abd51a358561b52d4d9ddc75b82b9749a3aba55a.tar.bz2 | |
Add a comment to the csv reader documentation that explains why the
treatment of newlines changed in 2.5. Pulled almost verbatim from a comment
by Andrew McNamara in <http://python.org/sf/1465014>.
| -rw-r--r-- | Doc/lib/libcsv.tex | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/Doc/lib/libcsv.tex b/Doc/lib/libcsv.tex index 65053c7..0e3294b 100644 --- a/Doc/lib/libcsv.tex +++ b/Doc/lib/libcsv.tex @@ -70,6 +70,17 @@ Parameters'' for details of these parameters. All data read are returned as strings. No automatic data type conversion is performed. + +\versionchanged[ +If literal newlines are important within a field, users need to read their +file in a way that preserves the newlines. The behavior before 2.5 would +introduce spurious characters into quoted fields, with no way for the user +to control that behavior. The previous behavior caused considerable +problems, particularly on platforms that did not use the unix line ending +conventions, or with files that originated on those platforms - users were +finding mysterious newlines where they didn't expect them. +]{2.5} + \end{funcdesc} \begin{funcdesc}{writer}{csvfile\optional{, |