Large Python codebase architecture visualization

“Show HN: A WYSIWYG word processor in Python Hi all, Finding a good data structure for a word processor is a difficult problem. My notebook diaries on the problem go back 25 years when I was frustrated with using Word for my diploma thesis - it was slow and unstable at that time. I ended up getting pretty hooked on the problem. Right now I’m taking a professional break and decided to finally use the time to push these ideas further, and build MiniWord — a WYSIWYG word processor in Python. My goal”

“FutureWarning: functools.partial will be a method descriptor in future Python versions; (MIIO) ### The problem ``` 2024-12-11 18:05:34.501 WARNING (ImportExecutor_0) [py.warnings] /srv/homeassistant/lib/python3.13/site-packages/miio/miot_device.py:23: FutureWarning: functools.partial will be a method descriptor in future Python versions; wrap it in enum.member() if you want to preserve the old behavior Bool = partial(_str2bool) ``` ### What version of Home Assistant Core has the is”

“Show HN: A Satellite View for Python Code Hi HN, I built ast-visualizer.com because I wanted a way to visualize the architecture/structure of a Python repo before dived into the code. Most tools tell you what the code does; I wanted to see how it's built. The Problem: Onboarding onto a large codebase is a nightmare. LLMs help with single functions, but they struggle to show you the God Objects, circular dependencies, or high-complexity hotspots across 50+ files. What it does: Dependenc”

“Show HN: Hm – a task runner with a Python DSL, growing into a CI/CD system Hi HN! My name is Marko and I am working on a CI/CD system at harmont.dev, a CI/CD system that sucks slightly less. As I've been working on the cloud, I realized that the CLI might be generally useful as a task runner, even if you don't care for our CI/CD, and that's what I'm sharing here! Every CI system I've used at Tesla, Bun, and mesa.dev has had the same problems: stateless and”

“Show HN: Gnosis, a knowledge base for what the code can't tell you For the past few years, I've been frustrated at how we document our products. The code can tell you what you ended up doing, maybe why you ended up doing it (if your team is disciplined about comments/documents), but it can't tell you why you didn't do what you didn't do . Time and time again, I've seen teams try to change something to a better way, only to realize why it was done the worse way in th”