Cannot write to a tun interface file

Open
#74,615 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by examining the two attached simple_incorrect.py files and the Python I/O behavior involved in writing to a tun interface file. Reproduce the reported failure on a system with a tun interface, then determine the expected write behavior and identify a focused regression test. The issue does not define a clear completion condition, so the desired fix needs confirmation.

Written by the indexing model from the issue text.

Description

topic-IO
BPO 30430
Nosy @pitrou
Files
  • simple_incorrect.py
  • simple_incorrect.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 2017-05-22.12:34:41.517>
labels = ['expert-IO']
title = 'Cannot write to a tun interface file'
updated_at = <Date 2017-05-22.15:36:01.391>
user = 'https://bugs.python.org/RmyLone'

    bugs.python.org fields:

    activity = <Date 2017-05-22.15:36:01.391>
actor = 'R\xc3\xa9my L\xc3\xa9one'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2017-05-22.12:34:41.517>
creator = 'R\xc3\xa9my L\xc3\xa9one'
dependencies = []
files = ['46885', '46886']
hgrepos = []
issue_num = 30430
keywords = []
message_count = 7.0
messages = ['294143', '294151', '294152', '294154', '294155', '294156', '294158']
nosy_count = 3.0
nosy_names = ['pitrou', 'neologix', 'R\xc3\xa9my L\xc3\xa9one']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue30430'
versions = ['Python 3.5']

    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.