
On Sat, Jun 06, 2020 at 09:31:36PM +0300, Bar Harel wrote:
It's one thing to say that the interpreter takes care of importing logging and setting up a basic logger, and that's great, but I still have to import logging and call the `logging.info(...)` functions, so what does this proposal give us, *in detail* please, and how do I use it?
You would be able to easily see the logs already generated by libraries, without needing to ever modify the Python files.
But if the libraries are already doing logging, can't I already do that? And if the libraries aren't doing logging, this won't magically add logging to them, will it? I think I need to see a (simplified!) but practical example of how this would work, from both the point of view of the library creator, and the library user. Thanks, -- Steven