email.header.decode_header sometimes returns bytes, sometimes str

Open
#65,691 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with email.header.decode_header and the dependent bpo-6302 proposal for email.utils.decode_header_as_string. Read the five-message issue thread to establish the intended return-type contract; done requires a decided behavior and corresponding documentation or implementation scope, but the payload names no files or tests.

Written by the indexing model from the issue text.

Description

3.7 (EOL) 3.8 (EOL) 3.9 (EOL) docs stdlib topic-email type-feature
BPO 21492
Nosy @warsaw, @ezio-melotti, @bitdancer, @berkerpeksag, @louisabraham
Dependencies
  • bpo-6302: Add decode_header_as_string method to email.utils
    		•

    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 2014-05-13.09:08:05.923>
labels = ['3.7', '3.8', 'expert-email', '3.9', 'type-feature', 'library', 'docs']
title = 'email.header.decode_header sometimes returns bytes, sometimes str'
updated_at = <Date 2019-06-07.18:44:38.667>
user = 'https://bugs.python.org/jimminter'

    bugs.python.org fields:

    activity = <Date 2019-06-07.18:44:38.667>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)', 'email']
creation = <Date 2014-05-13.09:08:05.923>
creator = 'jim_minter'
dependencies = ['6302']
files = []
hgrepos = []
issue_num = 21492
keywords = []
message_count = 5.0
messages = ['218419', '218442', '218450', '218451', '344522']
nosy_count = 7.0
nosy_names = ['barry', 'ezio.melotti', 'r.david.murray', 'docs@python', 'berker.peksag', 'jim_minter', 'louis.abraham@yahoo.fr']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue21492'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9']

    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.