PEP 383: socket module doesn't handle undecodable protocol or service names

Open
#53,869 2 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

Start by reading PEP 383 and the attached proto-service-pep383-3.2.diff from BPO issue 9660, then inspect how the current socket module handles protocol and service names. The work is done when those names follow the PEP 383 behavior and regression coverage verifies undecodable values.

Written by the indexing model from the issue text.

Description

extension-modules topic-socket type-bug
BPO 9660
Nosy @loewis, @vstinner, @tiran
Files
  • proto-service-pep383-3.2.diff: Handle socket protocol and service names according to PEP 383
    		•

    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 2010-08-22.18:26:00.732>
labels = ['extension-modules', 'type-bug']
title = "PEP 383: socket module doesn't handle undecodable protocol or service names"
updated_at = <Date 2013-07-06.00:30:51.702>
user = 'https://bugs.python.org/baikie'

    bugs.python.org fields:

    activity = <Date 2013-07-06.00:30:51.702>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2010-08-22.18:26:00.732>
creator = 'baikie'
dependencies = []
files = ['18608']
hgrepos = []
issue_num = 9660
keywords = ['patch']
message_count = 2.0
messages = ['114687', '114747']
nosy_count = 4.0
nosy_names = ['loewis', 'vstinner', 'baikie', 'christian.heimes']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue9660'
versions = ['Python 3.2', 'Python 3.3', 'Python 3.4']

    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.