Yes, a full-fledged Django project would have its own configuration files. This is an interesting question: on the one hand, we have to provide a short example, and that's why we're using django.conf.settings, as per Django docs. On the other hand, though, the reason we are providing examples for other frameworks should be that the user already uses one of them in their code and hence, in case of Django, has all these settings in separate files. This might mean that, for a user that doesn't care which app to use for routing of requests, any framework will do, but a user that already uses Django might not find the Django example useful. Then, instead of one example with some lines changed for the respective framework, this actually should expand into something of a tutorial (if you're using Django, but add these lines to urlpatterns, then add this to your settings file etc.). Which, in turn, sort of subverts the idea of having a simple usage example.