multiprocessing.Array misleading error message in slice assignment

Open
#76,186 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reviewing the original BPO issue 32005 and linked PR gh-110719, since the issue provides no file or test location. Done means resolving the misleading error message reported for multiprocessing.Array slice assignment and confirming the relevant behavior is covered.

Written by the indexing model from the issue text.

Description

3.10 3.11 3.9 (EOL) stdlib topic-multiprocessing type-bug
BPO 32005
Nosy @stevendaprano

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 2017-11-10.23:53:08.892>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = 'multiprocessing.Array misleading error message in slice assignment'
updated_at = <Date 2021-06-22.11:57:27.362>
user = 'https://github.com/stevendaprano'

bugs.python.org fields:

activity = <Date 2021-06-22.11:57:27.362>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-11-10.23:53:08.892>
creator = 'steven.daprano'
dependencies = []
files = []
hgrepos = []
issue_num = 32005
keywords = []
message_count = 1.0
messages = ['306066']
nosy_count = 1.0
nosy_names = ['steven.daprano']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue32005'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

Linked PRs
  • gh-110719
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.