Email does not apply policy to multipart messages with defects
Open
Nobody has claimed this yet.
3.8 (EOL)
topic-email
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43818 |
|---|---|
| Nosy | @warsaw, @bitdancer, @jishac |
| Files |
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-04-12.20:17:28.769>
labels = ['3.8', 'expert-email']
title = 'Email does not apply policy to multipart messages with defects'
updated_at = <Date 2022-03-28.19:43:44.147>
user = 'https://github.com/jishac'
bugs.python.org fields:
activity = <Date 2022-03-28.19:43:44.147>
actor = 'mdengler'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2021-04-12.20:17:28.769>
creator = 'jishac'
dependencies = []
files = ['49955']
hgrepos = []
issue_num = 43818
keywords = []
message_count = 2.0
messages = ['390897', '416204']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'mdengler', 'jishac']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue43818'
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 with the attached email.multipart.test.py script to reproduce the behavior, then trace the email component's handling of multipart messages with defects and policy application. Done means the reported case behaves according to the policy and has a regression test covering it.
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
- Mostly clear
- Newbie friendliness
- 35/100