email module should have a way to prepend and insert headers

Open
#62,339 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with Python's email module and review the linked suryak.patch, which proposes insert_header() to insert a header at the beginning. Check the existing header-manipulation behavior and discussion history first; the work is done when the module provides the requested prepend and insert capabilities with behavior consistent with its current API.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-feature
BPO 18139
Nosy @warsaw, @bitdancer
Files
  • suryak.patch: insert_header() to insert header at the beginning
  • 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-06-05.04:35:54.493>
    labels = ['type-feature', 'library', 'expert-email']
    title = 'email module should have a way to prepend and insert headers'
    updated_at = <Date 2016-08-22.15:32:58.051>
    user = 'https://bugs.python.org/kbandla'
    

    bugs.python.org fields:

    activity = <Date 2016-08-22.15:32:58.051>
    actor = 'barry'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)', 'email']
    creation = <Date 2013-06-05.04:35:54.493>
    creator = 'kbandla'
    dependencies = []
    files = ['34278']
    hgrepos = []
    issue_num = 18139
    keywords = ['patch']
    message_count = 10.0
    messages = ['190641', '190658', '190661', '190662', '212642', '212645', '212646', '212731', '273380', '273381']
    nosy_count = 4.0
    nosy_names = ['barry', 'r.david.murray', 'kbandla', 'suryak']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue18139'
    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.