Author vinay.sajip
Recipients bquinlan, brian.curtin, eric.araujo, georg.brandl, lukasz.langa, ncoghlan, pitrou, r.david.murray, vinay.sajip
Date 2010-12-27.14:37:53
SpamBayes Score 4.84962e-07
Marked as misclassified No
Message-id <1293460675.59.0.710512664265.issue10626@psf.upfronthosting.co.za>
In-reply-to
Content
The reason for the bad interaction is that some of the tests in test_logging disable all existing loggers (due to the configuration tests - disabling of existing loggers is explicitly tested for), but as a side effect this also disabled the concurrent.futures logger.

I've made a change to test_logging which preserves the disabled state of all existing loggers across tests, and now all is well when testing

regrtest.py test_concurrent_futures test_logging test_concurrent_futures

after applying Brian's patch of 24 Dec 2010.

The change has been checked into py3k (r87513). However, this raises the wider issue of other loggers in stdlib and the effect on them of logging configuration calls. I'll raise this on python-dev for discussion.
History
Date User Action Args
2010-12-27 14:37:55vinay.sajipsetrecipients: + vinay.sajip, georg.brandl, bquinlan, ncoghlan, pitrou, eric.araujo, r.david.murray, brian.curtin, lukasz.langa
2010-12-27 14:37:55vinay.sajipsetmessageid: <1293460675.59.0.710512664265.issue10626@psf.upfronthosting.co.za>
2010-12-27 14:37:53vinay.sajiplinkissue10626 messages
2010-12-27 14:37:53vinay.sajipcreate