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 vinay.sajip
Recipients benjamin.peterson, gvanrossum, pjenvey, vinay.sajip
Date 2009-10-14.05:55:31
SpamBayes Score 0.003138994
Marked as misclassified No
Message-id <1255499733.28.0.78291957074.issue7120@psf.upfronthosting.co.za>
In-reply-to
Content
I propose to fix it by just setting logRecord.processName to None for
now, which is what should happen if multiprocessing isn't available.

In environments where multiprocessing is not available,
logging.logMultiprocessing should be False, but that fix needs to go
into GAE, I guess?

Benjamin, I believe you added this change (in r70348), are you
comfortable with what I'm proposing? Anyone else have any objections?
History
Date User Action Args
2009-10-14 05:55:33vinay.sajipsetrecipients: + vinay.sajip, gvanrossum, pjenvey, benjamin.peterson
2009-10-14 05:55:33vinay.sajipsetmessageid: <1255499733.28.0.78291957074.issue7120@psf.upfronthosting.co.za>
2009-10-14 05:55:31vinay.sajiplinkissue7120 messages
2009-10-14 05:55:31vinay.sajipcreate