[issue31804] multiprocessing calls flush on sys.stdout at exit even if it is None (pythonw)

Pox TheGreat report at bugs.python.org
Tue Oct 17 10:59:34 EDT 2017


New submission from Pox TheGreat <poxthegreat at gmail.com>:

If you start Python by pythonw then sys.stdout and sys.stderr are set to None. If you also use multiprocessing then when the child process finishes BaseProcess._bootstrap calls sys.stdout.flush() and sys.stderr.flush() finally. This causes the process return code to be not zero (it is 1).

----------
components: Library (Lib)
files: process.py.patch
keywords: patch
messages: 304512
nosy: Pox TheGreat
priority: normal
severity: normal
status: open
title: multiprocessing calls flush on sys.stdout at exit even if it is None (pythonw)
type: crash
versions: Python 3.5
Added file: https://bugs.python.org/file47224/process.py.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31804>
_______________________________________


More information about the Python-bugs-list mailing list