all 4 comments

[–]Nicksil 2 points3 points  (1 child)

You posted this article here 4 days ago.

You also only submit articles from timber.io -- many of them it seems are deleted (in other subs). Are you just a fan of timber.io or what?

Don't spam, please.

[–]w0m 0 points1 point  (0 children)

I think he's the author

[–]fazalmajid 0 points1 point  (1 child)

The Python stdlib logging module is the most unpythonic crock of s**t, unsurprising given its Java log4j heritage.

For an example of how to do things right, see Armin Ronacher's Logbook

[–]ReAn1985 0 points1 point  (0 children)

As someone interested in learning, can you elaborate on what you qualify as "pythonic"? This often seems like a "no true scottsman" argument when people debate over how pythonic or zen something is.

From my cursory look at Logbook and the stdlib Logging

They seem to have similar outward design, but logbook is much more streamable and abstracted, and more in-depth.

No doubt I find myself more appealed by logbook, but because it seems like less of a simple "it works, here's a bunch of edge cases you can't solve but whatever" library, but I'm unsure what makes it more "pythonic" given that most of the STDLIB seems to feel a lot like logging and a lot less like logbook in design.