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 Pox TheGreat
Recipients Pox TheGreat, davin, pitrou, terry.reedy
Date 2018-01-10.09:33:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Retested it with a freshly installed 3.6.4 version. Used the following code to test:

import sys
import multiprocessing

def foo():
    return 'bar'

if __name__ == '__main__':
    proc = multiprocessing.Process(target=foo)
    with open('process_exit_code.txt', 'w') as f:
        f.write('\nprocess exit code: ')

It is very important to run the script with pythonw, not just with python. This is the content of the resulting process_exit_code.txt file on my machine:
3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:04:45) [MSC v.1900 32 bit (Intel)]
process exit code: 1

As it can be seen the problem was not fixed. The process exit code should be 0. By default the new multiprocessing process created uses the same interpreter as the creator process, so it uses pythonw too.
Date User Action Args
2018-01-10 09:33:29Pox TheGreatsetrecipients: + Pox TheGreat, terry.reedy, pitrou, davin
2018-01-10 09:33:29Pox TheGreatsetmessageid: <>
2018-01-10 09:33:29Pox TheGreatlinkissue31804 messages
2018-01-10 09:33:29Pox TheGreatcreate