The decode_header function does not always work correctly.
Open
Nobody has claimed this yet.
stdlib
topic-email
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34330 |
|---|---|
| Nosy | @warsaw, @bitdancer, @tirkarthi |
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 2018-08-03.14:40:05.783>
labels = ['expert-email']
title = 'The decode_header function does not always work correctly.'
updated_at = <Date 2018-08-05.05:03:04.276>
user = 'https://bugs.python.org/2'
bugs.python.org fields:
activity = <Date 2018-08-05.05:03:04.276>
actor = 'xtreak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2018-08-03.14:40:05.783>
creator = '\xd0\x92\xd0\xbb\xd0\xb0\xd0\xb4 \xd0\x9a2'
dependencies = []
files = []
hgrepos = []
issue_num = 34330
keywords = []
message_count = 1.0
messages = ['323056']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'xtreak', '\xd0\x92\xd0\xbb\xd0\xb0\xd0\xb4 \xd0\x9a2']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue34330'
versions = ['Python 2.7']
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 locating Python's email implementation of decode_header and determine which input case from the original bug report reproduces the incorrect behavior. The payload names no source file or test, so identify the relevant email tests before defining the expected decoded result and verifying the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100