Mailing List Archive

[issue27752] [doc] CSV DictReader default dialect name 'excel' is misleading, as MS Excel doesn't actually use ', ' as a separator.
Change by Irit Katriel <iritkatriel@yahoo.com>:


----------
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
title: CSV DictReader default dialect name 'excel' is misleading, as MS Excel doesn't actually use ',' as a separator. -> [doc] CSV DictReader default dialect name 'excel' is misleading, as MS Excel doesn't actually use ',' as a separator.
versions: +Python 3.11 -Python 2.7

_______________________________________
Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue27752>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
[issue27752] [doc] CSV DictReader default dialect name 'excel' is misleading, as MS Excel doesn't actually use ', ' as a separator. [ In reply to ]
Change by Jack DeVries <jdevries3133@gmail.com>:


----------
keywords: +patch
nosy: +jack__d
nosy_count: 3.0 -> 4.0
pull_requests: +25378
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26795

_______________________________________
Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue27752>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
[issue27752] [doc] CSV DictReader default dialect name 'excel' is misleading, as MS Excel doesn't actually use ', ' as a separator. [ In reply to ]
Jack DeVries <jdevries3133@gmail.com> added the comment:

If you need semicolon delimiters, can't you just pass ``delimiter=';'`` to the reader or writer? I don't think there's a need for a separate dialect class for that, since dialect classes should only provide a baseline for the most broad use cases. Users have plenty of options for extending or customizing behavior without adding more dialect classes.

I also think the docs around dialects are confusing. I remember being confused by them when I was learning! I made quite a few changes to try to add clarity around dialects to the documentation. Let me know if anybody has feedback!

----------

_______________________________________
Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue27752>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com