IDNA2008 encoding is missing

Offen
#61,507 37 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
15/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
networking

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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']

    Vorherrschende Sprache
    Python
    Sterne
    77.2k
    Forks
    36k
    Ø Merge
    1 T. 9 Std.
    Gemergte PRs (30 T.)
    558

    Beitragsleitfaden

    Beitragsleitfaden öffnen

    Erste Schritte

    1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
    2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
    3. Forken Sie das Repository und arbeiten Sie in einem Branch.
    4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

    Mehr aus python/cpython

    Alle Issues in python/cpython

    Ähnliche Issues

    Weitere Issues zu Python

    Neue Issues direkt in Ihr Postfach

    Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.