News for hackers. Stuff that matters.
Re:An Introduction to Scientific Python – Pandas by jeffwass on Monday July 04, 2016 @02:25AM (#12029147)
It's really too bad that the ASCII codes 29, 30, and 31 (Group, Record, and Unit separators) never took off, as this is exactly what they were designed for.

When implemented, they'd let you include commas, line feeds/carriage returns, etc within your data records.

Re:An Introduction to Scientific Python – Pandas by stinos on Monday July 04, 2016 @04:57AM (#12029543)
they'd let you include commas, line feeds/carriage returns, etc within your data records

And there would also be less ambiguity as to what seperator to use. I understand the popularity of CSV, but it's really not so nice to share data with. German customers want semicolons as a seperator, the US ones claims they are right 'because after all it is called comma-seperated and else I cannot import it in Excel' (sic). Etc.