I do not think Java is the only outlier here. In general library authors should never force a logger to write to anything. It should be a do-nothing logger. It

I do not think Java is the only outlier here. In general library authors should never force a logger to write to anything. It should be a do-nothing logger. It should provide a configuration so logs are going through the application utilizing the library. If I am wrong interpreting your comment, let me know. [1]: http://docs.python-guide.org/en/latest/writing/logging/#logging-in-a-library http://docs.python-guide.org/en/latest/writing/logging/#logg...