[PR #1576] [MERGED] Add structlog #3477

New Issue

GiteaMirror · 2026-04-15T09:27:59-05:00

GiteaMirror commented

2026-04-15 09:27:59 -05:00

📋 Pull Request Information

Original PR: https://github.com/vinta/awesome-python/pull/1576
Author: @rpdelaney
Created: 7/15/2020
Status: ✅ Merged
Merged: 7/15/2020
Merged by: @vinta

Base: master ← Head: structlog

📝 Commits (1)

bbab941 Add structlog

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

What is this Python project?

Originally proposed back in 2015 with #321, the project is much more mature now.

I will crib some from the why page for structlog which summarizes (a) why structured logging is good and (b) why structlog is good at structured logging.

Structured logging means that you don’t write hard-to-parse and hard-to-keep-consistent prose in your logs but that you log events that happen in a context instead...

structlog provides a handy interface for defining a structure for logging and then emitting log messages. It can also act as a handler for the built in logging module. It can handle encoding, capture user-defined elements of a call stack to log a context, pretty-print (including colorized) log messages for local development, format timestamps, filter log messages by level, and many more....

Testing mechanisms are provided that hook neatly into pytest.

What's the difference between this Python project and similar ones?

Structured logging! Here is a video about why structured logging is good, and why structlog is good at it.

--

Anyone who agrees with this pull request could submit an Approve review to it.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/vinta/awesome-python/pull/1576 **Author:** [@rpdelaney](https://github.com/rpdelaney) **Created:** 7/15/2020 **Status:** ✅ Merged **Merged:** 7/15/2020 **Merged by:** [@vinta](https://github.com/vinta) **Base:** `master` ← **Head:** `structlog` --- ### 📝 Commits (1) - [`bbab941`](https://github.com/vinta/awesome-python/commit/bbab941cc8f4dd249436241382f28b5c5d9eb819) Add structlog ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description ## What is this Python project? Originally proposed back in 2015 with #321, the project is much more mature now. I will crib some from the [why](https://www.structlog.org/en/stable/why.html) page for `structlog` which summarizes (a) why structured logging is good and (b) why `structlog` is good at structured logging. > Structured logging means that you don’t write hard-to-parse and hard-to-keep-consistent prose in your logs but that you log events that happen in a context instead... `structlog` provides a handy interface for defining a structure for logging and then emitting log messages. It can also act as a handler for the built in `logging` module. It can handle encoding, capture user-defined elements of a call stack to log a context, pretty-print (including colorized) log messages for local development, format timestamps, filter log messages by level, and many more.... Testing mechanisms are provided that hook neatly into `pytest`. ## What's the difference between this Python project and similar ones? Structured logging! [Here](https://www.youtube.com/watch?v=Y5eyEgyHLLo) is a video about why structured logging is good, and why `structlog` is good at it. -- Anyone who agrees with this pull request could submit an *Approve* review to it. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-15 09:27:59 -05:00

GiteaMirror closed this issue

2026-04-15 09:28:02 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-python#3477