multiprocessing.Connection does not communicate pipe closure between parent and child

Offen
#56,697 10 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
documentation

Rechercherichtung

No source file or test is named. Start by reading the multiprocessing.Connection documentation and the linked BPO issue, then reproduce the parent/child pipe-closure behavior to determine whether the documented behavior or implementation is incorrect. Done means the closure behavior is clearly resolved and covered by the appropriate documentation or test.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

3.10 3.8 (EOL) 3.9 (EOL) docs topic-multiprocessing type-bug
BPO 12488
Nosy @pitrou

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 2011-07-04.11:43:29.105>
labels = ['type-bug', '3.8', '3.9', '3.10', 'docs']
title = 'multiprocessing.Connection does not communicate pipe closure between parent and child'
updated_at = <Date 2020-11-14.11:11:23.404>
user = 'https://bugs.python.org/lcampagn'

bugs.python.org fields:

activity = <Date 2020-11-14.11:11:23.404>
actor = 'neologix'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2011-07-04.11:43:29.105>
creator = 'lcampagn'
dependencies = []
files = []
hgrepos = []
issue_num = 12488
keywords = []
message_count = 8.0
messages = ['139754', '139765', '139769', '139788', '139789', '139791', '139792', '159282']
nosy_count = 4.0
nosy_names = ['syeberman', 'pitrou', 'docs@python', 'lcampagn']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue12488'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

Vorherrschende Sprache
Python
Sterne
77.2k
Forks
36k
Ø Merge
1 T. 9 Std.
Gemergte PRs (30 T.)
558

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus python/cpython

Alle Issues in python/cpython

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.