[New-bugs-announce] [issue28326] multiprocessing.Process depends on sys.stdout being open

ProgVal report at bugs.python.org
Sat Oct 1 07:45:34 EDT 2016


New submission from ProgVal:

Hello,

The following code:

import sys
import multiprocessing

sys.stdout.close()

def foo():
    pass

p = multiprocessing.Process(target=foo)
p.start()


Crashes with:

Traceback (most recent call last):
  File "foo.py", line 10, in <module>
    p.start()
  File "/usr/lib/python3.5/multiprocessing/process.py", line 105, in start
    self._popen = self._Popen(self)
  File "/usr/lib/python3.5/multiprocessing/context.py", line 212, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "/usr/lib/python3.5/multiprocessing/context.py", line 267, in _Popen
    return Popen(process_obj)
  File "/usr/lib/python3.5/multiprocessing/popen_fork.py", line 17, in __init__
    sys.stdout.flush()
ValueError: I/O operation on closed file.


This bug has been reported to me on a daemonized program (written prior to PEP 3143).

----------
components: Library (Lib)
messages: 277807
nosy: Valentin.Lorentz
priority: normal
severity: normal
status: open
title: multiprocessing.Process depends on sys.stdout being open
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28326>
_______________________________________


More information about the New-bugs-announce mailing list