>> We'll have to consider whether universal newline mode - along with an >> implicit restriction in possible EOL sequences - is the way to go. aahz> How about EOL is None means universal newlines and is the default? My worry is that if you have (for example) a \n embedded in a field when the EOL character is a \r that the parsing would get screwed up. That \n is a character in a field, not the end of a record. (Such fields may always have to be quoted, but I'm not sure.) At this level it's really an issue for Andrew MacNamara or Dave Cole. I'm not too familiar with the underlying C code. I suspect in the end that the csv module may have to do all it's own I/O. That would be a PITA, but might be required. Skip
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