Antti Haapala added the comment:
Excel's behaviour has always been locale-dependent. If the user's locale uses ,
as the decimal mark , then ; has been used as the column separator in "C"SV.
However, even if you use autodetection with sniff, it is impossible to detect
with 100 % accuracy, e.g, is the following csv row comma or semicolon separated:
1,2;3;4,5;6,7;8;9
The dialect could be documented better though, as currently it simply says:
The excel class defines the usual properties of an Excel-generated CSV
file. It is registered with the dialect name 'excel'.
And there really should be a separate dialect for Excel-semicolon separated
values, as a couple billion people would see ; in their CSV.
----------
nosy: +ztane
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27752>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
