utf8 in BytesGenerator
Open
Nobody has claimed this yet.
3.9 (EOL)
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43333 |
|---|---|
| Nosy | @warsaw, @bitdancer, @iritkatriel |
| 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-02-26.21:50:13.675>
labels = ['type-bug', 'expert-email', '3.9']
title = 'utf8 in BytesGenerator'
updated_at = <Date 2022-02-24.13:20:32.697>
user = 'https://bugs.python.org/darcybeurle'
bugs.python.org fields:
activity = <Date 2022-02-24.13:20:32.697>
actor = 'chrisstaunton1990'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2021-02-26.21:50:13.675>
creator = 'darcy.beurle'
dependencies = []
files = ['50641']
hgrepos = []
issue_num = 43333
keywords = []
message_count = 4.0
messages = ['387749', '411464', '411513', '413906']
nosy_count = 5.0
nosy_names = ['barry', 'r.david.murray', 'iritkatriel', 'darcy.beurle', 'chrisstaunton1990']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43333'
versions = ['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 running the sample script in sample.py and inspecting the BytesGenerator entry point involved in the email component. Determine the expected UTF-8 behavior from the reproduced result and existing project guidance; the issue is done when that behavior is corrected and covered by an appropriate 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