Idle: use pipes instead of sockets to talk with user subprocess

Open
#63,023 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
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
desktop

Research direction

Start by reading the attached Carlson.py and tracing the IDLE subprocess communication code it exercises. Determine the expected pipe-based behavior, then run the relevant IDLE subprocess tests or reproducer and confirm that user subprocesses communicate through pipes without regressions.

Written by the indexing model from the issue text.

Description

topic-IDLE type-bug
BPO 18823
Nosy @terryjreedy, @ezio-melotti, @asvetlov, @serhiy-storchaka
Files
  • Carlson.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-08-23.23:35:04.085>
labels = ['expert-IDLE', 'type-bug', '3.10']
title = 'Idle: use pipes instead of sockets to talk with user subprocess'
updated_at = <Date 2020-06-06.16:26:52.685>
user = 'https://github.com/terryjreedy'

    bugs.python.org fields:

    activity = <Date 2020-06-06.16:26:52.685>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IDLE']
creation = <Date 2013-08-23.23:35:04.085>
creator = 'terry.reedy'
dependencies = []
files = ['34654']
hgrepos = []
issue_num = 18823
keywords = []
message_count = 6.0
messages = ['196055', '215062', '215069', '215123', '336154', '370832']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'ezio.melotti', 'asvetlov', 'tshepang', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue18823'
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.