[issue26648] csv.reader Error message indicates to use deprecated

2016-03-27 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: When this error is triggered at all? -- ___ Python tracker ___ ___

[issue26648] csv.reader Error message indicates to use deprecated

2016-03-27 Thread SilentGhost
SilentGhost added the comment: Ah, the bit about csv module doing it's own newline handling is what I missed. Here is the updated patch. -- Added file: http://bugs.python.org/file42306/issue26648_2.diff ___ Python tracker

[issue26648] csv.reader Error message indicates to use deprecated

2016-03-27 Thread Martin Panter
Martin Panter added the comment: Isn’t using newline=None a way to produce the error in the first place? Silent Ghost: see the footnote . Reading with newline=None translates newlines. Writing with newline=None produces CRLFs on Windows. I

[issue26648] csv.reader Error message indicates to use deprecated

2016-03-27 Thread SilentGhost
SilentGhost added the comment: While the 'U' mode has been deprecated it doesn't mean that your example doesn't run in 3.5 - it runs just fine and will keep doing so until 4.0 I'm attaching patch that suggests using newline=None (even though it's a default value for open), as that what seems

[issue26648] csv.reader Error message indicates to use deprecated

2016-03-26 Thread Philip Martin
New submission from Philip Martin: Currently, the error message: _csv.Error: new-line character seen in unquoted field - do you need to open the file in universal-newline mode? is cryptic in that universal line mode has been deprecated, and will not run in Python 3.5., i.e.: