Improve reporting of broken stdout pipe during interpreter shutdown

Open
#55,589 16 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start by reviewing python-sigint_and_epipe_straces.txt and flush_stdout_at_shutdown.patch, the historical evidence and proposed change attached to this issue. Determine the current interpreter-shutdown behavior for a broken stdout pipe and define improved reporting before validating the result with an appropriate regression test.

Written by the indexing model from the issue text.

Description

topic-IO type-bug
BPO 11380
Nosy @terryjreedy, @ncoghlan, @pitrou, @rbtcollins, @florentx, @vadmium
Files
  • python-sigint_and_epipe_straces.txt: strace of issue in 3.2.2, 3.1.2, and 2.5.2
  • flush_stdout_at_shutdown.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-03-03.01:32:45.546>
labels = ['type-bug', 'expert-IO']
title = 'Improve reporting of broken stdout pipe during interpreter shutdown'
updated_at = <Date 2018-06-16.10:13:08.003>
user = 'https://bugs.python.org/ulidtko'

    bugs.python.org fields:

    activity = <Date 2018-06-16.10:13:08.003>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2011-03-03.01:32:45.546>
creator = 'ulidtko'
dependencies = []
files = ['24517', '31853']
hgrepos = []
issue_num = 11380
keywords = ['patch']
message_count = 16.0
messages = ['129930', '130083', '153320', '198316', '198332', '198338', '198339', '198345', '198347', '198349', '213109', '248574', '248579', '248625', '248626', '319729']
nosy_count = 11.0
nosy_names = ['terry.reedy', 'ncoghlan', 'pitrou', 'rbcollins', 'zzzeek', 'flox', 'ulidtko', 'martin.panter', 'Jeremy.Fishman', 'daumiller', 'Christopher.Heiny']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue11380'
versions = ['Python 2.7']

    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.