>IMHO these test cases are *WRONG* and it's a worry that they "work" with
>the current csv module :-(
Those tests are not "wrong" - they verify that we produce the same result
as Excel when presented with those inputs, which was one of the design
goals of the module (and is an important considera
On 12/03/2007 1:41 PM, Andrew McNamara wrote:
>
> The point was to produce the same results as Excel. Sure, Excel probably
> doesn't generate crap like this itself, but 3rd parties do, and people
> complain if we don't parse it just like Excel (sigh).
Let's put a little flesh on those a's and b's
On 12/03/2007 1:01 PM, [EMAIL PROTECTED] wrote:
> I decided it would be worthwhile to have a csv module written in Python (no
> C underpinnings) for a number of reasons:
>
> * It will probably be easier to add Unicode support to a Python version
>
> * More people will be able to read/grok
John> IMHO these test cases are *WRONG* and it's a worry that they
John> "work" with the current csv module :-(
That's my take on things as well, though as Andrew pointed out, given those
invalid inputs Excel will produce those wacky outputs. I verified that on
my Mac a few minutes ago.
