Email package issue with Outlook msg files
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
topic-email
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44685 |
|---|---|
| Nosy | @warsaw, @bitdancer, @heghineGhazaryan |
| 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-07-20.16:02:15.163>
labels = ['3.7', '3.8', 'expert-email', '3.9']
title = 'Email package issue with Outlook msg files'
updated_at = <Date 2021-07-24.01:08:00.480>
user = 'https://github.com/heghineGhazaryan'
bugs.python.org fields:
activity = <Date 2021-07-24.01:08:00.480>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2021-07-20.16:02:15.163>
creator = 'heghine'
dependencies = []
files = ['50167']
hgrepos = []
issue_num = 44685
keywords = []
message_count = 2.0
messages = ['397885', '398110']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'heghine']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue44685'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9']
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 reproducing the problem in Python's email package with the attached msg file.msg. The report does not specify the expected behavior or name a test, so clarify the intended Outlook MSG handling before identifying the relevant parser code and defining a regression test.
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