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 iritkatriel
Recipients Delgan, iritkatriel, serhiy.storchaka, vinay.sajip
Date 2020-09-07.17:42:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1599500541.61.0.791963173624.issue38762@roundup.psfhosted.org>
In-reply-to
Content
As the PR currently is, it will, unless you turn this off by setting logging.logMultiprocessing=False.

The other alternative we are discussing is: revert back to not importing multiprocessing if it's not there.

If it's there we use it, but if it's not we set processName to something like f"pid={os.getpid()}" instead of "MainThread".

(1) os is already imported in logging.

(2) In most cases where multiprocessing is not imported it's because there is only one process, so processName will not likely be used as all.

(3) In the edge case of shutdown or someone clearing sys.modules the processName will not be pretty, but it will at least be correct.
History
Date User Action Args
2020-09-07 17:42:21iritkatrielsetrecipients: + iritkatriel, vinay.sajip, serhiy.storchaka, Delgan
2020-09-07 17:42:21iritkatrielsetmessageid: <1599500541.61.0.791963173624.issue38762@roundup.psfhosted.org>
2020-09-07 17:42:21iritkatriellinkissue38762 messages
2020-09-07 17:42:21iritkatrielcreate