[issue27508] process thread with implicit join is killed unexpectedly

Tim Peters added the comment: Ah - good catch! I'm closing this as a duplicate of bug18966. The real mystery now is why the threads _don't_ terminate early under Windows 3.5.2 - heh. -- resolution: -> duplicate status: open -> closed superseder: -> Threads within multiprocessing Pr

[issue27508] process thread with implicit join is killed unexpectedly

R. David Murray added the comment: On my gentoo system it prints hi four times in 2.7, and 3.2 through 3.6. I suspect multiprocessing is killing threads, daemon or not, when the main process thread ends. I expect that's a feature, although I didn't find it documented. Ah, found the explanat

[issue27508] process thread with implicit join is killed unexpectedly

Tim Peters added the comment: Curious: under Python 2.7.11 on Windows, the threads also terminate early (they run "forever" - as intended - under 3.5.2). -- ___ Python tracker

[issue27508] process thread with implicit join is killed unexpectedly

Changes by Tim Peters : -- components: +Library (Lib) type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue27508] process thread with implicit join is killed unexpectedly

Tim Peters added the comment: Note: this started on stackoverflow: https://stackoverflow.com/questions/38356584/python-multiprocessing-threading-code-exits-early I may be missing something obvious, but the only explanation I could think of for the behavior seen on Ubuntu is that the threads i

[issue27508] process thread with implicit join is killed unexpectedly

New submission from JA: On Ubuntu 16.04 python '3.5.1+ (default, Mar 30 2016, 22:46:26) \n[GCC 5.3.1 20160330]' The following code prints "hi" 4 times: import multiprocessing import time import threading class dumb(threading.Thread): def __init__(self): super(dumb, self).__ini