Possible race condition in Pool

Open
#69,240 10 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
backend

Research direction

Start by reviewing BPO issue 25053 and the Python Library (Lib) implementation of Pool; the issue does not name a source file or test. Reproduce the suspected race under concurrent use, identify the affected behavior, and add a regression test that demonstrates the corrected behavior before considering the issue done.

Written by the indexing model from the issue text.

Description

3.8 (EOL) stdlib topic-multiprocessing type-bug
BPO 25053
Nosy @applio

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 2015-09-10.11:33:42.241>
labels = ['3.8', 'type-bug', 'library']
title = 'Possible race condition in Pool'
updated_at = <Date 2020-11-15.22:27:31.079>
user = 'https://bugs.python.org/StanislawIzaakPitucha'

bugs.python.org fields:

activity = <Date 2020-11-15.22:27:31.079>
actor = 'anilb'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-09-10.11:33:42.241>
creator = 'Stanislaw Izaak Pitucha'
dependencies = []
files = []
hgrepos = []
issue_num = 25053
keywords = []
message_count = 9.0
messages = ['250362', '250393', '250436', '381029', '381030', '381031', '381032', '381035', '381037']
nosy_count = 3.0
nosy_names = ['davin', 'Stanislaw Izaak Pitucha', 'anilb']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25053'
versions = ['Python 3.4', 'Python 3.5', 'Python 3.8']

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.