Repository navigation
Closed
Closed
Copy link
Labels
3.10 (EOL)end of lifeend of life3.11only security fixesonly security fixes3.9 (EOL)end of lifeend of lifeeasystdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directorytype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2021-10-11.11:09:03.163>
created_at = <Date 2013-12-20.04:38:14.524>
labels = ['easy', 'type-bug', '3.9', '3.10', '3.11', 'library']
title = 'csv: Confusing error message when giving invalid quotechar in initializing dialect'
updated_at = <Date 2021-10-11.11:09:03.163>
user = 'https://github.com/vajrasky'bugs.python.org fields:
activity = <Date 2021-10-11.11:09:03.163>
actor = 'corona10'
assignee = 'none'
closed = True
closed_date = <Date 2021-10-11.11:09:03.163>
closer = 'corona10'
components = ['Library (Lib)']
creation = <Date 2013-12-20.04:38:14.524>
creator = 'vajrasky'
dependencies = []
files = ['33226', '33227']
hgrepos = []
issue_num = 20028
keywords = ['patch', 'easy']
message_count = 11.0
messages = ['206663', '206667', '206668', '401605', '403534', '403535', '403536', '403537', '403539', '403540', '403651']
nosy_count = 6.0
nosy_names = ['r.david.murray', 'serhiy.storchaka', 'vajrasky', 'corona10', 'miss-islington', 'iritkatriel']
pr_nums = ['28705', '28830', '28831', '28832', '28833', '28834', '28835']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20028'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']Metadata
Metadata
Assignees
Labels
3.10 (EOL)end of lifeend of life3.11only security fixesonly security fixes3.9 (EOL)end of lifeend of lifeeasystdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directorytype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Activity
vajrasky commentedon Dec 20, 2013
Hey, that's not true. Quotechar can be None.
That's not strictly true. Quotechar can be 0-character string in certain situation.
Python 2.7 suffers the same issue.
vajrasky commentedon Dec 20, 2013
Here is the preliminary patch for Python 3.3 and 3.4.
vajrasky commentedon Dec 20, 2013
Here is the preliminary patch for Python 2.7.
iritkatriel commentedon Sep 10, 2021
The patch needs to be converted to a GitHub PR.
Reproduced on 3.11:
[-]Confusing error message when giving invalid quotechar in initializing csv dialect[/-][+]csv: Confusing error message when giving invalid quotechar in initializing dialect[/+]corona10 commentedon Oct 9, 2021
New changeset 34bbc87 by Dong-hee Na in branch 'main':
bpo-20028: Improve error message of csv.Dialect when initializing (GH-28705)
34bbc87
corona10 commentedon Oct 9, 2021
New changeset ec04db7 by Dong-hee Na in branch 'main':
bpo-20028: Keep original exception when PyUnicode_GetLength return -1 (GH-28832)
ec04db7
miss-islington commentedon Oct 9, 2021
New changeset 6f3bc5e by Miss Islington (bot) in branch '3.9':
bpo-20028: Improve error message of csv.Dialect when initializing (GH-28705)
6f3bc5e
miss-islington commentedon Oct 9, 2021
New changeset 8772935 by Miss Islington (bot) in branch '3.10':
bpo-20028: Improve error message of csv.Dialect when initializing (GH-28705)
8772935
corona10 commentedon Oct 9, 2021
New changeset c80f0b7 by Dong-hee Na in branch '3.10':
[3.10] bpo-20028: Keep original exception when PyUnicode_GetLength return -1 (GH-28832) (GH-28834)
c80f0b7
corona10 commentedon Oct 9, 2021
New changeset e4fcb6f by Dong-hee Na in branch '3.9':
[3.9] bpo-20028: Keep original exception when PyUnicode_GetLength return -1 (GH-28832) (GH-28835)
e4fcb6f
corona10 commentedon Oct 11, 2021
New changeset ab62051 by Dong-hee Na in branch 'main':
bpo-20028: Empty escapechar/quotechar is not allowed for csv.Dialect (GH-28833)
ab62051
GPHemsley-RELX commentedon Dec 19, 2023
What was the motivation here for disallowing an empty escapechar? It seems the original report was intending to point out misleading error messages, not a desired change in functionality.