email.feedparser: support RFC 6532 section 3.5
Open
Nobody has claimed this yet.
3.11
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44660 |
|---|---|
| Nosy | @warsaw, @terryjreedy, @bitdancer, @f18a14c09s |
| 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-17.03:52:51.007>
labels = ['type-bug', 'expert-email', '3.11']
title = 'email.feedparser: support RFC 6532 section 3.5'
updated_at = <Date 2022-04-02.02:44:28.408>
user = 'https://github.com/f18a14c09s'
bugs.python.org fields:
activity = <Date 2022-04-02.02:44:28.408>
actor = 'f18a14c09s'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2021-07-17.03:52:51.007>
creator = 'f18a14c09s'
dependencies = []
files = []
hgrepos = []
issue_num = 44660
keywords = ['patch']
message_count = 9.0
messages = ['397693', '398094', '398100', '398101', '398103', '398107', '398108', '398773', '416533']
nosy_count = 6.0
nosy_names = ['barry', 'terry.reedy', 'r.david.murray', 'python-dev', 'virusdetected1337', 'f18a14c09s']
pr_nums = ['27208']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44660'
versions = ['Python 3.11']
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 reading RFC 6532 section 3.5 and the email.feedparser implementation, then review the existing python/cpython#27208 pull request. Done means the parser supports the specified behavior with appropriate tests, but the issue does not name files or tests to change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, internationalization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100