email/charset.py convert() patch

Open
#42,985 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading email/charset.py and the attached charset.py.patch to understand the proposed convert() change. Use ja-nonlegit.py as the example input and compare its behavior with the patch; done means the intended character conversion behavior is defined and supported without regressing existing email handling.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-feature
BPO 1443875
Nosy @loewis, @warsaw, @vstinner, @bitdancer
Files
  • charset.py.patch: charset.py.patch
  • ja-nonlegit.py: non-legitimate ja characters example
  • 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 2006-03-06.04:41:30.000>
    labels = ['type-feature', 'library', 'expert-email']
    title = 'email/charset.py convert() patch'
    updated_at = <Date 2019-07-29.12:00:52.206>
    user = 'https://bugs.python.org/tkikuchi'
    

    bugs.python.org fields:

    activity = <Date 2019-07-29.12:00:52.206>
    actor = 'vstinner'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)', 'email']
    creation = <Date 2006-03-06.04:41:30.000>
    creator = 'tkikuchi'
    dependencies = []
    files = ['7052', '7053']
    hgrepos = []
    issue_num = 1443875
    keywords = ['patch']
    message_count = 6.0
    messages = ['49660', '49661', '49662', '49663', '49664', '348645']
    nosy_count = 5.0
    nosy_names = ['loewis', 'barry', 'tkikuchi', 'vstinner', 'r.david.murray']
    pr_nums = []
    priority = 'low'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue1443875'
    versions = ['Python 3.3']
    

    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.