email.parse part.get_filename() fails to unwrap long attachment file names (legacy API)
Open
Nobody has claimed this yet.
topic-email
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40359 |
|---|---|
| Nosy | @warsaw, @bitdancer |
| 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 2020-04-22.00:26:27.411>
labels = ['expert-email']
title = 'email.parse part.get_filename() fails to unwrap long attachment file names (legacy API)'
updated_at = <Date 2020-04-28.12:27:30.371>
user = 'https://bugs.python.org/matt-davis'
bugs.python.org fields:
activity = <Date 2020-04-28.12:27:30.371>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-04-22.00:26:27.411>
creator = 'matt-davis'
dependencies = []
files = ['49083']
hgrepos = []
issue_num = 40359
keywords = []
message_count = 6.0
messages = ['366963', '366965', '366966', '367117', '367493', '367523']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'matt-davis']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue40359'
versions = ['Python 3.6']
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 linked mwe.py minimal working example and reproduce the failure through email.parse and part.get_filename(), focusing on the legacy email API. Trace how the long attachment filename is handled and verify that the completed behavior unwraps it correctly without regressing existing filename parsing.
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