multiprocessing.Connection.poll raises BrokenPipeErr... | python/cpython

説明

BPO	41008
Nosy	@zanchey

^{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 2020-06-17.14:59:25.730>
labels = ['type-bug', '3.9']
title = 'multiprocessing.Connection.poll raises BrokenPipeError on Windows'
updated_at = <Date 2020-06-17.14:59:25.730>
user = 'https://github.com/zanchey'

bugs.python.org fields:

activity = <Date 2020-06-17.14:59:25.730>
actor = 'zanchey'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2020-06-17.14:59:25.730>
creator = 'zanchey'
dependencies = []
files = []
hgrepos = []
issue_num = 41008
keywords = []
message_count = 1.0
messages = ['371748']
nosy_count = 1.0
nosy_names = ['zanchey']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41008'
versions = ['Python 3.9']

はじめの一歩

issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。

着手することを issue にコメントします — 二人が同じ作業をするのを防げます。

リポジトリをフォークし、ブランチを切って変更します。

issue 番号を参照したプルリクエストを送ります。

調査の方向性

Start at the multiprocessing.Connection.poll entry point and reproduce the reported behavior on Windows. Trace why polling raises BrokenPipeError, then verify that polling a broken connection behaves as intended without introducing regressions. The issue provides no source file or test location, so locating the implementation and relevant tests is part of the initial investigation.

索引モデルが issue の本文から書いたものです。

評価

技術スタック

python

領域

operating-systems

issue の種類

バグ

難易度

4/5

見積もり時間

3〜5日

活発さ

停滞

明瞭さ

説明が足りない

初心者へのやさしさ

30/100

multiprocessing.Connection.poll raises BrokenPipeError on Windows

説明

コントリビューションガイド

はじめの一歩

調査の方向性

評価

新しい issue をメールで受け取る