Terminal apps used to mean raw curses calls and a lot of pain. Today, Python’s Textual and Rich libraries have flipped that. In under 50 lines of Python you get a full-screen app with styled layouts, widgets, keyboard control, and live data. No web browser. No Electron. No JavaScript. This post walks through both libraries, shows how they fit together, and builds up to a full working example you can extend right away.

You can find and fix Python memory leaks with three tools that pair well: memray for flame graphs, tracemalloc for line-level tracking, and objgraph for object reference maps. Start with memray to spot the hungry functions. Drop into tracemalloc to find the exact lines. End with objgraph to see why objects won’t get collected. Pair this with generators, __slots__, memory-mapped files, and chunked reads to cut peak memory by 50-80% in data-heavy apps.

You can self-host a private PyPI registry with pypiserver and a private npm registry with Verdaccio . Both run on a single box or inside Docker containers. You get three wins that public registries cannot match: faster installs from a LAN cache, a safe home for private packages, and cover against outages, typosquatting, and supply chain attacks. Both tools are free, open-source, and take under 30 minutes to set up.

Testcontainers spins up real databases and services as Docker containers inside your test suite. Tests run against production-grade PostgreSQL, Redis, or Kafka instead of flaky mocks. The testcontainers-python v4.14.2 library works with pytest . It automates the container life cycle. You get isolated, reproducible integration tests that catch bugs unit tests miss.

Below: setup with pytest, testing services beyond databases, performance patterns, and CI/CD configuration.

Why Mocks and In-Memory Databases Are Not Enough

Mocking db.execute() only checks if your code calls the function. It does not check if the SQL is valid. It also misses schema errors and type mismatches. You might have passing tests while your queries fail in production.

Property-based testing with Hypothesis lets you define what your code must do. One classic rule: “encode, then decode, and you get the same input back.” Hypothesis then makes up hundreds of random inputs and hunts for cases that break the rule. You don’t write test cases by hand. You sketch the shape of valid inputs. The tool finds the off-by-one bugs, the odd Unicode strings, and the edge cases hiding in your code.

You can build a polished, interactive command-line app in Go by pairing Cobra for command structure with Bubble Tea for the terminal UI. Cobra covers argument parsing, subcommands, flags, and auto-generated shell completions. Bubble Tea adds spinners, tables, text inputs, progress bars, and keyboard navigation on top. The result is one static binary. It runs in scripts and CI when called plainly, and shows a full terminal interface when a person runs it.