This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients paul.moore, ronaldoussoren, schwemro, steve.dower, tim.golden, zach.ware
Date 2018-04-16.15:27:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523892457.72.0.682650639539.issue33286@psf.upfronthosting.co.za>
In-reply-to
Content
Multiprocessing by default uses the fork system call to start new processes on Linux. This system call is not available on Windows, and there multiprocessing starts a fresh interpreter (see <https://docs.python.org/3.6/library/multiprocessing.html#multiprocessing.get_start_method>). 

I'm also on macOS, and cannot reproduce the problem there even when using the 'spawn' method there by adding some lines to the start of your script (before the other import statements):

import multiprocessing
if __name__ == "__main__":
    multiprocessing.set_start_method('spawn')

But: I have a fairly old version of 3.6 on my machine.
History
Date User Action Args
2018-04-16 15:27:37ronaldoussorensetrecipients: + ronaldoussoren, paul.moore, tim.golden, zach.ware, steve.dower, schwemro
2018-04-16 15:27:37ronaldoussorensetmessageid: <1523892457.72.0.682650639539.issue33286@psf.upfronthosting.co.za>
2018-04-16 15:27:37ronaldoussorenlinkissue33286 messages
2018-04-16 15:27:37ronaldoussorencreate