CSV sniffing falsely detects space as a delimiter
Open
Nobody has claimed this yet.
3.13
3.14
3.15
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44677 |
|---|---|
| Nosy | @rhettinger, @ptokarski |
| PRs |
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 = None
created_at = <Date 2021-07-19.17:40:33.684>
labels = ['3.8', 'type-bug', 'library']
title = 'CSV sniffing falsely detects space as a delimiter'
updated_at = <Date 2021-07-22.02:15:15.339>
user = 'https://github.com/ptokarski'
bugs.python.org fields:
activity = <Date 2021-07-22.02:15:15.339>
actor = 'rhettinger'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-07-19.17:40:33.684>
creator = 'pt12lol'
dependencies = []
files = []
hgrepos = []
issue_num = 44677
keywords = ['patch']
message_count = 4.0
messages = ['397821', '397859', '397860', '397974']
nosy_count = 3.0
nosy_names = ['rhettinger', 'python-dev', 'pt12lol']
pr_nums = ['27256']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44677'
versions = ['Python 3.8']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the CSV sniffing case described in the issue and review PR #27256, which is linked in the migrated report. Trace the relevant Python CSV library behavior and add or update a regression test so a space is not falsely selected as the delimiter; done means the reported case passes with the intended delimiter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100