No handlers could be found for logger "cookielib"
I first saw this last night, when running the -all tests on WinXP, CVS HEAD: ... test_univnewlines test_unpack test_urllib test_urllib2 No handlers could be found for logger "cookielib" HERE test_urllibnet ... It didn't act the same way in isolation. Anyone have a clue? The test still passes, it just spits out that unhelpful logger output -- sometimes.
Tim Peters wrote:
I first saw this last night, when running the -all tests on WinXP, CVS HEAD:
... test_univnewlines test_unpack test_urllib test_urllib2 No handlers could be found for logger "cookielib" HERE test_urllibnet ...
It didn't act the same way in isolation. Anyone have a clue? The test still passes, it just spits out that unhelpful logger output -- sometimes.
See the thread at http://mail.python.org/pipermail/python-dev/2004-July/046396.html for an explanation of the message. Basically means no default handler is specified. -Brett
[Tim]
I first saw this last night, when running the -all tests on WinXP, CVS HEAD:
... test_univnewlines test_unpack test_urllib test_urllib2 No handlers could be found for logger "cookielib" HERE test_urllibnet ...
It didn't act the same way in isolation. Anyone have a clue? The test still passes, it just spits out that unhelpful logger output -- sometimes.
[Brett]
See the thread at http://mail.python.org/pipermail/python-dev/2004-July/046396.html for an explanation of the message. Basically means no default handler is specified.
Ya, I know about that. The real questions are two others: 1. Why does it only appear *sometimes*, depending on how the test suite is run? It always appears when running -uall now. It never appears when running the surrounding tests in isolation. 2. Since it started happening very recently (I've run the full test suite often the last week), does it ring a bell with anyone who checked something in very recently? Somebody changed something relevant very recently.
participants (2)
-
Brett C. -
Tim Peters