IDNA2008 encoding is missing

Open
#61,507 37 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

Start by reviewing the existing IDNA-related work in the linked pull requests #25208, #25210, and #25211, then inspect the referenced idna_translate.py file. The issue is in patch review and remains open, so the intended completion criteria must be recovered from those changes and the historical discussion.

Written by the indexing model from the issue text.

Description

stdlib topic-SSL topic-unicode type-feature
BPO 17305
Nosy @loewis, @gpshead, @tiran, @bitdancer, @njsmith, @asvetlov, @ambv, @socketpair, @berkerpeksag, @Lukasa, @wumpus, @miss-islington, @epicfaace, @akulakov, @case
PRs
  • python/cpython#25208
  • python/cpython#25210
  • python/cpython#25211
  • Files
  • idna_translate.py
  • 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-02-27.01:32:46.318>
    labels = ['expert-SSL', 'type-feature', 'library', '3.10']
    title = 'IDNA2008 encoding is missing'
    updated_at = <Date 2021-11-04.19:39:59.773>
    user = 'https://bugs.python.org/marten'
    

    bugs.python.org fields:

    activity = <Date 2021-11-04.19:39:59.773>
    actor = 'case'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)', 'SSL']
    creation = <Date 2013-02-27.01:32:46.318>
    creator = 'marten'
    dependencies = []
    files = ['29256']
    hgrepos = []
    issue_num = 17305
    keywords = ['patch']
    message_count = 35.0
    messages = ['183104', '183106', '183144', '183147', '183149', '183159', '183160', '183199', '183202', '205009', '205034', '217092', '217218', '278493', '279904', '310923', '310924', '310943', '310988', '311007', '311009', '311013', '349642', '349643', '349840', '349855', '349886', '370635', '389932', '390246', '390288', '390291', '390296', '391980', '396587']
    nosy_count = 20.0
    nosy_names = ['loewis', 'gregory.p.smith', 'christian.heimes', 'r.david.murray', 'njs', 'asvetlov', 'lukasz.langa', 'socketpair', 'underrun', 'berker.peksag', 'era', 'marten', 'Lukasa', 'wumpus', 'SamWhited', 'Socob', 'miss-islington', 'epicfaace', 'andrei.avk', 'case']
    pr_nums = ['25208', '25210', '25211']
    priority = 'high'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue17305'
    versions = ['Python 3.10']
    

    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.