email: collapse_rfc2231_value has inconsistent unquoting

Open
#73,206 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

The issue identifies collapse_rfc2231_value in Python's email component, but it names no source file, test, or precise expected behavior. First clarify which quoted and unquoted inputs are inconsistent, then locate the function and its tests; done means the unquoting behavior is consistent and covered by a regression test.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-bug
BPO 29020
Nosy @warsaw, @bitdancer, @elafontaine

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 2016-12-20.00:30:12.317>
labels = ['type-bug', 'expert-email']
title = 'email: collapse_rfc2231_value has inconsistent unquoting'
updated_at = <Date 2017-01-03.12:22:37.774>
user = 'https://bugs.python.org/bpoaugust'

bugs.python.org fields:

activity = <Date 2017-01-03.12:22:37.774>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2016-12-20.00:30:12.317>
creator = 'bpoaugust'
dependencies = []
files = []
hgrepos = []
issue_num = 29020
keywords = []
message_count = 5.0
messages = ['283658', '283936', '284293', '284311', '284501']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'bpoaugust', 'Eric Lafontaine']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29020'
versions = ['Python 3.5']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.