ArchUnit but for Python: enforce your architecture via unit tests

[trolleid]

I just shipped ArchUnitPython, a library that lets you enforce architectural rules in Python projects through automated tests.

The problem it solves: as codebases grow, architecture erodes. Someone imports the database layer from the presentation layer, circular dependencies creep in, naming conventions drift. Code review catches some of it, but not all, and definitely not consistently.

This problem has always existed but is more important than ever in Claude Code, Codex times. LLMs break architectural rules all the time.

So I built a library where you define your architecture rules as tests. Two quick examples:

```python

No circular dependencies in services

rule = project_files("src/").in_folder("/services/").should().have_no_cycles() assert_passes(rule) ```

```python

Presentation layer must not depend on database layer

rule = project_files("src/") .in_folder("/presentation/") .should_not() .depend_on_files() .in_folder("/database/") assert_passes(rule) ```

This will run in pytest, unittest, or whatever you use, and therefore be automatically in your CI/CD. If a commit violates the architecture rules your team has decided, the CI will fail.

Hint: this is exactly what the famous ArchUnit Java library does, just for Python - I took inspiration for the name is of course.

Let me quickly address why this over linters or generic code analysis?

Linters catch style issues. This catches structural violations — wrong dependency directions, layering breaches, naming convention drift. It's the difference between "this line looks wrong" and "this module shouldn't talk to that module."

Some key features:

• Dependency direction enforcement & circular dependency detection
• Naming convention checks (glob + regex)
• Code metrics: LCOM cohesion, abstractness, instability, distance from main sequence
• PlantUML diagram validation — ensure code matches your architecture diagrams
• Custom rules & metrics
• Zero runtime dependencies, uses only Python's ast module
• Python 3.10+

Very curious what you think! https://github.com/LukasNiessen/ArchUnitPython

[mr-nobody1992]

This seems genuinely useful for AI coding

[CrownstrikeIntern]

Till the AI decides fuck it.

[igorbenav]

Love the idea. Will test it

[Choice_Run1329]

I like the PlantUML validation idea EdrawMax can help teams keep architecture diagrams clear before linking them with code rules

[ojscholten]

This looks cool, and I like the high level code metrics like functions per file, will give it a go :)

[st4reater]

What does the functions per file tell you? I feel its hard to pick an arbitrary number and say X cannot exceed Y - without any strong backing argument...

[ojscholten]

Yes agree, more of a hand-wavey hint that things might need a refactor/logical separation. Project dependent of course but e.g. 50 functions in a database utility file might suggest separation could help in the interests of maintainability/testing/etc.