Email policy option for disabling RFC2231 Mime parameter folding
Open
Nobody has claimed this yet.
3.10
3.9 (EOL)
topic-email
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 45794 |
|---|---|
| Nosy | @warsaw, @bitdancer |
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-11-12.11:56:23.253>
labels = ['expert-email', '3.10', '3.9']
title = 'Email policy option for disabling RFC2231 Mime parameter folding'
updated_at = <Date 2021-11-12.11:56:23.253>
user = 'https://bugs.python.org/Ezekeel'
bugs.python.org fields:
activity = <Date 2021-11-12.11:56:23.253>
actor = 'Ezekeel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2021-11-12.11:56:23.253>
creator = 'Ezekeel'
dependencies = []
files = []
hgrepos = []
issue_num = 45794
keywords = []
message_count = 1.0
messages = ['406205']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'Ezekeel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue45794'
versions = ['Python 3.9', 'Python 3.10']
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
The payload identifies only the email component and the RFC2231 MIME parameter-folding behavior; no source file or test is named. Start by locating the email policy and parameter-folding implementation, then inspect existing policy tests to determine how the disabling option should be represented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100