Makes sense.
However, light FWs such as Tornado (which I like a lot, and prefers over Flask BTW) have a really small learning curve for a basic usage
(i.e. serving dynamic pages with the help of templates). If you're already familiar with Django, you'll be productive with Tornado is less than one hour, if not shorter.
If you have the option to invest a bit of time, it deserves a look because you'll get the ROI of having one more weapon in your arsenal. You'll thus be able to select the best suited option instead of relying on the same one every time. Although Django is really
great (I work a lot with it for years for my job as well as for private projects, and I really enjoy it), there are situations it's not the optimal choice. For instance, it can be a bit overkill when you don't have to play with a data model justifying
an ORM and such.
One important word about Tornado, and why I like it so much : it is based on the asynchronous paradigm and despite being single thread and single process
(although it supports a multi-process execution mode for taking advantage of multi-cores CPUs) it is able to serve a lot of requests thanks to this. This is especially true when these requests are IO bound
(e.g. DB access, network requests...). Knowing such an architecture and knowing how to properly implement request handlers to leverage its power is IMHO a valuable experience. Tornado is amazing when your target is an embedded system with constrained
resources, such as a Raspberry Pi or alike. I've developed several real world apps in this context and it plays amazingly well.
Even if Tornado has not as many batteries included as Django (it brings nothing for data access f.i.) it comes with a lot of valuable features inside in addition to templating and request serving
(CSRF, CORS, sessions, user authentication, asynchronous network clients, Web sockets, I18N support, UI modules,...). In addition, you don't need to put a WSGI server in front, since it includes its own asynchronous production grade server
(not a dev server such as Django's runserver but a real production one).
Maybe all this looks
a bit like Tornado propaganda or Django bashing. It's neither of these of course, but only my own experience.
Best regards
Eric