commit | 6831d6bc7f4ee97ee854ddaa50f47ec4fb781cd2 | [log] [tgz] |
---|---|---|
author | Vinay Sajip <vinay_sajip@yahoo.co.uk> | Thu Dec 04 20:32:18 2008 +0000 |
committer | Vinay Sajip <vinay_sajip@yahoo.co.uk> | Thu Dec 04 20:32:18 2008 +0000 |
tree | 4d236b05638e3375df311c4a93339b413a248976 | |
parent | 97f49f4be7ab6d4b570029be4b4439cc29be2f74 [diff] |
Took Nick Coghlan's advice about importing warnings globally in logging, to avoid the possibility of race conditions: "This could deadlock if a thread spawned as a side effect of importing a module happens to trigger a warning. warnings is pulled into sys.modules as part of the interpreter startup - having a global 'import warnings' shouldn't have any real effect on logging's import time."