Message93967
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? |
|
Date |
User |
Action |
Args |
2009-10-14 05:55:33 | vinay.sajip | set | recipients:
+ vinay.sajip, gvanrossum, pjenvey, benjamin.peterson |
2009-10-14 05:55:33 | vinay.sajip | set | messageid: <1255499733.28.0.78291957074.issue7120@psf.upfronthosting.co.za> |
2009-10-14 05:55:31 | vinay.sajip | link | issue7120 messages |
2009-10-14 05:55:31 | vinay.sajip | create | |
|