[issue28326] multiprocessing.Process depends on sys.stdout being open

Antoine Pitrou added the comment: This is now fixed in 3.6 and 3.7. Closing! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue28326] multiprocessing.Process depends on sys.stdout being open

Antoine Pitrou added the comment: New changeset 34ef6da8f5fb03b83268bd35b77fb2183c748b70 by Antoine Pitrou in branch '3.6': [3.6] bpo-28326: Fix multiprocessing.Process when stdout and/or stderr is closed or None. (GH-4073). (#4075) https://github.com/python/cpython/commit/34ef6da8f5fb03b832

[issue28326] multiprocessing.Process depends on sys.stdout being open

Change by Antoine Pitrou : -- pull_requests: +4045 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue28326] multiprocessing.Process depends on sys.stdout being open

Antoine Pitrou added the comment: New changeset daeefd2e049b74340307481112a39f77de0f4769 by Antoine Pitrou in branch 'master': bpo-28326: Fix multiprocessing.Process when stdout and/or stderr is closed or None. (#4073) https://github.com/python/cpython/commit/daeefd2e049b74340307481112a39f77d

[issue28326] multiprocessing.Process depends on sys.stdout being open

Change by Antoine Pitrou : -- pull_requests: +4043 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue28326] multiprocessing.Process depends on sys.stdout being open

Antoine Pitrou added the comment: In issue31804, we see that sys.stdout and sys.stderr can sometimes simply be None, so we must check for that too. -- nosy: +pitrou versions: -Python 3.5 ___ Python tracker

[issue28326] multiprocessing.Process depends on sys.stdout being open

Changes by Tiago Antao : -- versions: +Python 3.6, Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue28326] multiprocessing.Process depends on sys.stdout being open

Changes by Tiago Antao : -- pull_requests: +1515 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue28326] multiprocessing.Process depends on sys.stdout being open

Tiago Antao added the comment: This is the first patch that I am submitting. More than willing to do any changes deemed necessary... -- ___ Python tracker ___ __

[issue28326] multiprocessing.Process depends on sys.stdout being open

Terry J. Reedy added the comment: Patch looks plausible to me. The flush calls definitely need to be guarded. -- nosy: +terry.reedy stage: -> patch review type: -> behavior ___ Python tracker ___

[issue28326] multiprocessing.Process depends on sys.stdout being open

Tiago Antao added the comment: I made a small patch for this. This is the first time I submit one, so please be careful with this... -- keywords: +patch nosy: +tiagoantao Added file: http://bugs.python.org/file44919/mp.patch ___ Python tracker

[issue28326] multiprocessing.Process depends on sys.stdout being open

Changes by James Lu : -- nosy: +James Lu ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue28326] multiprocessing.Process depends on sys.stdout being open

Changes by Ned Deily : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue28326] multiprocessing.Process depends on sys.stdout being open

Changes by Mariatta Wijaya : -- nosy: +Mariatta ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue28326] multiprocessing.Process depends on sys.stdout being open

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 p.start() File "/usr/lib/