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 Kallah
Recipients Kallah, paul.moore, steve.dower, steven.daprano, tim.golden, zach.ware
Date 2020-01-08.10:17:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1578478668.25.0.429996946382.issue39255@roundup.psfhosted.org>
In-reply-to
Content
The difference here is that on Windows y will never change, it will stay 1 forever while on Unix systems y will increment. Having done a bit more research it seems this is due to the way multiprocessing works on Windows vs Unix systems. In unix systems the new thread is a fork of the parent while in Windows it is a whole new process built from scratch (if I am understanding it correctly). I am not going to close it as I am unsure if it is by design that Windows and Unix python acts differently.
History
Date User Action Args
2020-01-08 10:17:48Kallahsetrecipients: + Kallah, paul.moore, tim.golden, steven.daprano, zach.ware, steve.dower
2020-01-08 10:17:48Kallahsetmessageid: <1578478668.25.0.429996946382.issue39255@roundup.psfhosted.org>
2020-01-08 10:17:48Kallahlinkissue39255 messages
2020-01-08 10:17:48Kallahcreate