empty local-part in addr_spec displayed incorrectly
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
stdlib
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38232 |
|---|---|
| Nosy | @warsaw, @bitdancer, @maxking, @andreitroiebbc |
| 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 2019-09-20.14:34:10.438>
labels = ['3.8', 'type-bug', '3.7', 'expert-email', '3.9']
title = 'empty local-part in addr_spec displayed incorrectly'
updated_at = <Date 2019-10-05.01:18:00.344>
user = 'https://github.com/andreitroiebbc'
bugs.python.org fields:
activity = <Date 2019-10-05.01:18:00.344>
actor = 'maxking'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2019-09-20.14:34:10.438>
creator = 'andreitroiebbc'
dependencies = []
files = ['48617']
hgrepos = []
issue_num = 38232
keywords = []
message_count = 3.0
messages = ['352852', '353003', '353983']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'maxking', 'andreitroiebbc']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38232'
versions = ['Python 3.6', '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 with the attached example_parser.py and reproduce how an addr_spec with an empty local-part is displayed. Trace the relevant email parsing or formatting path in CPython, then add coverage showing the corrected representation for this case.
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
- 35/100