Comment 5 for bug 314959

twisted log failures are rich and not well bridgable to python logging (in terms of capturing everything from the failure dict etc), so no, this shouldn't be a logger: it should be twisted specific and not bridge to python logging at all. I'm deleting the code entirely now, in favour of python-oops-twisted which includes a twisted specific non python logging implementation.