On 10:35 pm, email@example.com wrote:
It is not hard to force an import of warnings to use the pure Python version and totally ignore the C implementation. See test_warnings on how to pull that off. Then you can do your hack of overriding warn_explicit().
Benjamin Peterson's recommendation sounds like the winner (since we need to do *something* different in 2.6 anyway). Forcing the import leads to a bunch of import-ordering problems, since the testing tool itself wants to emit warnings, and self-test, and then it has to import the module _and_ set an attribute on the SUT module...
Thanks for the tip, though.