BytesGenerator does not handle 'binary' CTE correctly

Open
#63,086 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the linked BPO issue 18886 and locate BytesGenerator in Python's email package. Read the existing handling of the 'binary' content-transfer encoding and determine the expected behavior from the issue discussion; the work is done when that behavior is implemented and covered by an appropriate regression test.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-feature
BPO 18886
Nosy @warsaw, @bitdancer, @nathanielmanistaatgoogle

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 2013-08-30.20:37:30.754>
labels = ['type-feature', 'expert-email']
title = "BytesGenerator does not handle 'binary' CTE correctly"
updated_at = <Date 2015-10-15.01:01:03.106>
user = 'https://github.com/bitdancer'

bugs.python.org fields:

activity = <Date 2015-10-15.01:01:03.106>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2013-08-30.20:37:30.754>
creator = 'r.david.murray'
dependencies = []
files = []
hgrepos = []
issue_num = 18886
keywords = []
message_count = 7.0
messages = ['196572', '212697', '212717', '212724', '253021', '253022', '253024']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'suryak', 'Nathaniel Manista']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue18886'
versions = ['Python 3.6']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.