What design patterns or ergonomics in Python libraries make them feel clunky to use?

I’m interested in developer ergonomics rather than performance or raw capability. Specifically, what API design choices, patterns, or conventions in Python libraries make routine tasks feel more cumbersome than they should be?

Examples might include inconsistent interfaces, excessive boilerplate, unclear abstractions, surprising defaults, or anything else that adds friction to common workflows.

I’m looking for concrete patterns or experiences rather than complaints about specific projects.

Posted Feb 26, 2026, 3:20 AM UTC

56
Loading comments…