Possible problem in documentation of module subprocess, method send_signal

Open
#57,577 8 comments 0 reactions 1 assignee View on GitHub

@briancurtin is already working on this.

Since Nov 11, 2011.

Assessment

This issue has not been assessed yet.

Description

3.10 3.9 (EOL) docs OS-windows topic-subprocess type-bug
BPO 13368
Nosy @briancurtin, @eryksun
Files
  • proc_group_ctrl_c.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 = 'https://github.com/briancurtin'
    closed_at = None
    created_at = <Date 2011-11-08.03:23:14.309>
    labels = ['3.10', 'type-bug', '3.9', 'OS-windows', 'docs']
    title = 'Possible problem in documentation of module subprocess, method send_signal'
    updated_at = <Date 2021-02-24.21:50:23.591>
    user = 'https://bugs.python.org/elibendersky'
    

    bugs.python.org fields:

    activity = <Date 2021-02-24.21:50:23.591>
    actor = 'eryksun'
    assignee = 'brian.curtin'
    closed = False
    closed_date = None
    closer = None
    components = ['Documentation', 'Windows']
    creation = <Date 2011-11-08.03:23:14.309>
    creator = 'eli.bendersky'
    dependencies = []
    files = ['41242']
    hgrepos = []
    issue_num = 13368
    keywords = []
    message_count = 7.0
    messages = ['147272', '147425', '147432', '194314', '213288', '255903', '387640']
    nosy_count = 5.0
    nosy_names = ['eli.bendersky', 'brian.curtin', 'docs@python', 'eryksun', 'nitika']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue13368'
    versions = ['Python 3.9', '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.