Took Nick Coghlan's advice about importing warnings globally in logging, to avoid...
commit0328e0cd7f26dfd6c1f5dbd9ca95537e2bd4d40f
authorvinay.sajip <vinay.sajip@6015fed2-1504-0410-9fe1-9d1591cc4771>
Thu, 4 Dec 2008 20:32:18 +0000 (4 20:32 +0000)
committervinay.sajip <vinay.sajip@6015fed2-1504-0410-9fe1-9d1591cc4771>
Thu, 4 Dec 2008 20:32:18 +0000 (4 20:32 +0000)
treed23da84613a20810d1f9b09ec2e8380cc674e921
parente37bc4a1d6ed753787f50f9f3e9ba1b1efb735bf
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."

git-svn-id: http://svn.python.org/projects/python/trunk@67537 6015fed2-1504-0410-9fe1-9d1591cc4771
Lib/logging/__init__.py
Misc/NEWS