Inspired by FastAPI and Kombu, Propan was created to simplify Message Brokers' code writing and to provide a helpful development toolkit, which existed only in HTTP-frameworks world until now.

It's designed to create reactive microservices around Messaging.

It is a modern, high-level framework on top of popular specific Python brokers libraries, based on pydantic, FastAPI, and pytest concepts.

I guess I knew the whole "you can't use next on iterables" in the sense that I've never tried it.

I TIL'd about the default value for next.

At least I posted it to !programming_horror@programming.dev first!

Part 2: https://programming.dev/post/792914

Once you've installed it, pytest will produce nice colourised diffs for any assert == :

😍

Via https://mastodon.social/@hynek/110479665200902390

Instantly spin-up a GraphQL API server by pointing PostGraphile at your existing PostgreSQL database

You can also follow the project on Mastodon: https://fosstodon.org/@graphile

The challenge: https://www.pgsqlphriday.com/2023/05/pgsql-phriday-009/

Another Phriday in the books, and it's time to see what all happened:

• Hari Kiran offered an introduction to the concepts and processes used in schema evolution with examples showing how to use Flyway, a popular Java-based tool.
• Grant Fritchey discussed what it means to roll a change back, why catastrophic failures are the good kind of failure, and how to work with deployment processes to adapt to failures and roll the database forward to a good state instead of trying to turn back time.
• Michael Christofides wrote about table stakes for database automation and his hopes for better integration of performance testing in automated change management.
• Andy Atkinson ran through the entire prompt item by item! Read it for a detailed look at Rails migrations in situ -- who writes them, who reviews them, what kinds of problems happen, and how to validate successful changes.
• Ryan Booz gave me ERWin flashbacks and proclaimed a decalogue for the aspiring database automator, from the foundational on up. No comment on whether I've ever achieved #7 without painstakingly restoring manual production dumps.
• finally, I covered the ideas powering a few less-usual schema evolution tools.