[issue10626] Bad interaction between test_logging and test_concurrent_futures

Brian Quinlan added the comment: Fixed in r87556. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-b

[issue10626] Bad interaction between test_logging and test_concurrent_futures

Vinay Sajip added the comment: 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 lo

[issue10626] Bad interaction between test_logging and test_concurrent_futures

Brian Quinlan added the comment: Sorry for being AWOL for so long. Attached is a patch that doesn't install a handler and checks stderr for the exception output. Unfortunately, it looks like the logging tests are still messing things up: ./python.exe -m test test_concurrent_futures test_concu

[issue10626] Bad interaction between test_logging and test_concurrent_futures

Vinay Sajip added the comment: s/logger of last resort/handler of last resort/ -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue10626] Bad interaction between test_logging and test_concurrent_futures

Vinay Sajip added the comment: I've added the logging code to implement and use a logger of last resort as discussed on the thread for http://bit.ly/last-resort-handler into the py3k branch, r87157. Gist of differences is available at https://gist.github.com/736120 - so Brian could remove the

[issue10626] Bad interaction between test_logging and test_concurrent_futures

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10626] Bad interaction between test_logging and test_concurrent_futures

Nick Coghlan added the comment: Yeah, I think that comment was just a mistaken impression on my part. Definitely something odd going on with the test interaction though. -- ___ Python tracker

[issue10626] Bad interaction between test_logging and test_concurrent_futures

Vinay Sajip added the comment: I will take a look at test_logging tidying up after itself, though the intention is to leave things as they were found (this is done in setUp/tearDown, and if it doesn't tidy up properly, that would be a bug). As already explained in logging's documentation, the

[issue10626] Bad interaction between test_logging and test_concurrent_futures

Changes by Nick Coghlan : -- title: test_concurrent_futures implicitly installs a logging handler on import -> Bad interaction between test_logging and test_concurrent_futures ___ Python tracker __