socket.getsockopt may require custom buffer contents

Open
#57,254 4 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
networking

Research direction

Start by reviewing the linked getsockopt_buffer_input.patch and getsockopt_buffer_input_v2.patch, then locate the current socket.getsockopt implementation and its tests. Confirm the intended behavior from the old BPO issue before changing anything; done means custom buffer contents are supported and the behavior is covered by relevant tests.

Written by the indexing model from the issue text.

Description

extension-modules topic-socket type-feature
BPO 13045
Nosy @pitrou
Files
  • getsockopt_buffer_input.patch
  • getsockopt_buffer_input_v2.patch
    		•

    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 2011-09-25.17:12:20.269>
labels = ['extension-modules', 'type-feature']
title = 'socket.getsockopt may require custom buffer contents'
updated_at = <Date 2011-10-05.16:45:31.804>
user = 'https://bugs.python.org/ximaera'

    bugs.python.org fields:

    activity = <Date 2011-10-05.16:45:31.804>
actor = 'neologix'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2011-09-25.17:12:20.269>
creator = 'ximaera'
dependencies = []
files = ['23243', '23306']
hgrepos = []
issue_num = 13045
keywords = ['patch']
message_count = 4.0
messages = ['144526', '144824', '144828', '144958']
nosy_count = 4.0
nosy_names = ['pitrou', 'neologix', 'python-dev', 'ximaera']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue13045'
versions = ['Python 3.2']

    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.