Mercurial > cpython-lru_cache-weakref
diff Doc/lib/libcsv.tex @ 39323:930bb1eb8dd5 legacy-trunk
Redo the comment about the 2.5 change in quoted-newline handling.
| author | Andrew McNamara <andrewm@object-craft.com.au> |
|---|---|
| date | Mon, 31 Jul 2006 02:27:48 +0000 |
| parents | 4e3ad65f55e8 |
| children | 7f04793fe135 |
line wrap: on
line diff
--- a/Doc/lib/libcsv.tex Mon Jul 31 01:46:03 2006 +0000 +++ b/Doc/lib/libcsv.tex Mon Jul 31 02:27:48 2006 +0000 @@ -72,13 +72,15 @@ 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} +The parser is now stricter with respect to multi-line quoted +fields. Previously, if a line ended within a quoted field without a +terminating newline character, a newline would be inserted into the +returned field. This behaviour caused problems when reading files +that embed carriage-return characters within fields, so in 2.5 the +behaviour was changed to return the field without inserting newlines. As +a consequence, if newlines embedded within fields are important, the +input should be split into lines in a manner which preserves the newline +characters.]{2.5} \end{funcdesc}
