subject:"\[issue24948\] Multiprocessing not timely flushing stack trace to stderr"

[issue24948] Multiprocessing not timely flushing stack trace to stderr

2015-08-27 Thread Memeplex

New submission from Memeplex: Related to but not the same than https://bugs.python.org/issue13812. Try this: ``` import multiprocessing as mp import time def g(): time.sleep(100) def f(): mp.Process(target=g).start() 1/0 mp.Process(target=f).start() ``` It won't show the ZeroDi

[issue24948] Multiprocessing not timely flushing stack trace to stderr

2015-08-27 Thread Memeplex

Memeplex added the comment: One possible fix to multiprocessing/process.py: < try: < self.run() < exitcode = 0 < finally: < util._exit_function() --- > self.run() > exitcode = 0 274a272 >

[issue24948] Multiprocessing not timely flushing stack trace to stderr

2015-08-27 Thread Jon Brandvein

Changes by Jon Brandvein : -- nosy: +brandjon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue24948] Multiprocessing not timely flushing stack trace to stderr

2015-09-12 Thread Davin Potts

Davin Potts added the comment: If I understand your motivations correctly, I'd restate them as: you want a mechanism for being immediately notified of an exception in a parent process without waiting on any child processes of that parent to finish and furthermore propose this should be the de