python / python/cpython

Include thread_name_prefix in the concurrent.futures.ThreadPoolExecutor example 17.4.2.1

Open
#73,470 6 comments 0 reactions 1 assignee View on GitHub

@Mariatta is already working on this.

Since Apr 10, 2019.

3.7 (EOL) 3.8 (EOL) docs topic-multiprocessing type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 29284
Nosy @gpshead, @jftuga, @applio, @Mariatta, @csabella
Files
  • ThreadPoolExec_Example.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/Mariatta'
    closed_at = None
    created_at = <Date 2017-01-16.16:42:44.559>
    labels = ['3.8', 'type-feature', '3.7', 'docs']
    title = 'Include thread_name_prefix  in the concurrent.futures.ThreadPoolExecutor example 17.4.2.1'
    updated_at = <Date 2019-04-10.12:08:39.841>
    user = 'https://github.com/jftuga'
    

    bugs.python.org fields:

    activity = <Date 2019-04-10.12:08:39.841>
    actor = 'cheryl.sabella'
    assignee = 'Mariatta'
    closed = False
    closed_date = None
    closer = None
    components = ['Documentation']
    creation = <Date 2017-01-16.16:42:44.559>
    creator = 'jftuga'
    dependencies = []
    files = ['46377']
    hgrepos = []
    issue_num = 29284
    keywords = []
    message_count = 6.0
    messages = ['285572', '286006', '291605', '298733', '298748', '339854']
    nosy_count = 6.0
    nosy_names = ['gregory.p.smith', 'docs@python', 'jftuga', 'davin', 'Mariatta', 'cheryl.sabella']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue29284'
    versions = ['Python 3.7', 'Python 3.8']
    

    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.

    Assessment

    This issue has not been assessed yet.

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.