// the take
drf-yasg generates OpenAPI 2.0 (Swagger) specs directly from DRF serializers and views, serving both swagger-ui and ReDoc from within your Django app. It's for DRF shops that want auto-generated interactive API docs without a separate docs pipeline. The library is mature and battle-tested but deliberately frozen at OpenAPI 2.0.
Nested serializer introspection actually works — it follows the full serializer graph rather than flattening everything to 'object'. The inspector chain is genuinely extensible: you can slot in custom field inspectors at any point without monkey-patching. Built-in per-user schema caching via Django's cache backend means serving the schema at scale is not an afterthought. The test project is a real working Django app with migrations and multiple serializer patterns, not just a hello-world fixture.
OpenAPI 2.0 only — the README itself tells you to go use drf-spectacular instead if you're starting fresh, which is a pretty clear signal about the project's trajectory. Versioning support is limited to URLPathVersioning and NamespaceVersioning; anything custom and you're on your own. The per-user schema caching model (separate cache entry per user) will eat memory fast on a large user base. Static assets (swagger-ui, ReDoc) are vendored into the package at fixed versions, so you're stuck with whatever UI version shipped with that release until you upgrade the whole library.
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →