>Then that person needs to specify '\r' as EOL (and open the file as >binary). There's no one-size fits all and yes, you normally do need to >quote string fields with embedded newlines with CSV. The csv module, as defined in 2.3, takes an iterable as the source of input lines. It doesn't make sense to then attempt additional EOL processing within the csv module - the current EOL processing in the csv module is a hang-over from it's past life as a stand-alone module that worked with 1.5.2, etc. I would propose that we remove most of the EOL processing from the csv module, making it simply ignore any terminal whitespace characters. If someone has EOL conventions that aren't catered to by the Python universal newline code, they can supply an alternate iterable source of lines. This should make the csv module behave as other parts of python behave (less nasty surprises). -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4