concurrent.futures `wait` and `as_completed` depend on private api

Open
#66,918 9 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
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reviewing non-magic-waiters.patch and the current concurrent.futures implementation of wait and as_completed. Compare how the patch removes private API dependencies and verify that the affected behavior remains covered; done means the two helpers no longer depend on private APIs.

Written by the indexing model from the issue text.

Description

3.7 (EOL) stdlib topic-multiprocessing type-bug
BPO 22729
Nosy @gpshead, @brianquinlan, @pitrou, @asvetlov, @nathanielmanistaatgoogle
Files
  • non-magic-waiters.patch: wait and as_completed implemented using callbacks
  • 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 2014-10-25.20:41:39.989>
    labels = ['3.7', 'type-bug', 'library']
    title = 'concurrent.futures `wait` and `as_completed` depend on private api'
    updated_at = <Date 2019-05-07.16:28:33.760>
    user = 'https://bugs.python.org/bwhmather'
    

    bugs.python.org fields:

    activity = <Date 2019-05-07.16:28:33.760>
    actor = 'bquinlan'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2014-10-25.20:41:39.989>
    creator = 'bwhmather'
    dependencies = []
    files = ['37016']
    hgrepos = []
    issue_num = 22729
    keywords = ['patch']
    message_count = 9.0
    messages = ['230016', '233896', '251218', '294568', '303567', '303580', '303585', '303589', '341776']
    nosy_count = 6.0
    nosy_names = ['gregory.p.smith', 'bquinlan', 'pitrou', 'asvetlov', 'bwhmather', 'Nathaniel Manista']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue22729'
    versions = ['Python 3.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.