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 davin
Recipients barry, davin, kapilt, miss-islington, ned.deily, pitrou, ronaldoussoren
Date 2018-12-09.15:13:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Do we really need to disable the running of test_multiprocessing_fork entirely on MacOS?

My understanding so far is that not *all* of the system libraries on the mac are spinning up threads and so we should expect that there are situations where fork alone may be permissible, but of course we don't yet know what those are.  Pragmatically speaking, I have not yet seen a report of test_multiprocessing_fork tests triggering this problem but I would like to see/hear that when it is observed (that's my pitch for leaving the tests enabled).
Date User Action Args
2018-12-09 15:13:53davinsetrecipients: + davin, barry, ronaldoussoren, pitrou, ned.deily, miss-islington, kapilt
2018-12-09 15:13:53davinsetmessageid: <>
2018-12-09 15:13:53davinlinkissue33725 messages
2018-12-09 15:13:53davincreate