This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients bobbyocean, r.david.murray, serhiy.storchaka, skip.montanaro
Date 2016-07-21.17:11:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469121108.78.0.483958760943.issue27580@psf.upfronthosting.co.za>
In-reply-to
Content
Bobby: Skip is one of the authors of the csv module, and has been maintaining it since it was added to the standard library.  He knows whereof he speaks: there is no standard for csv (as noted in the article you link), and all csv parsers that want to be interoperable refer back to Microsoft's implementation when dealing with any quirks.  That implementation currently is Excel.

That said, your are right that others have adopted the format, and there is an argument to be made that we don't have to *limit* ourselves to what Microsoft supports.  Although we probably don't want to be emitting stuff that they don't without being explicit about it.
History
Date User Action Args
2016-07-21 17:11:48r.david.murraysetrecipients: + r.david.murray, skip.montanaro, serhiy.storchaka, bobbyocean
2016-07-21 17:11:48r.david.murraysetmessageid: <1469121108.78.0.483958760943.issue27580@psf.upfronthosting.co.za>
2016-07-21 17:11:48r.david.murraylinkissue27580 messages
2016-07-21 17:11:48r.david.murraycreate