It is difficult to choose one, so I'm adding some key points:
* Internationalziation: so simple to use.
* Timezones: this is a nightmare, and Django has this just right.
* ORM: I even use the ORM in stand-alone applications because is easy, powerful and not so limited as every other ORM. Simple operations are easy, complex things too: Q and F expressions, filters, related entities access and retrieval, caching,...
* Middleware: I won't write again a piece of software to manage sessions. It supports automatic CRSF and XSS mitigations, form checking, in-memory caching for static content,...
* Admin interface: the admin interface is so powerful that many applications only need a small customization and you already have a complete product. This is a god-send for managemente applications, for example, or for rapid prototypes.
The templating system is not the most powerful, I tend to rely on Jinja or others because of flexibility and speed. This is a point that should be improved.
The ORM has support for automatic schema migrations, this is good but it has some issues that you have to track manually. I remember it had an issue where some data could be lost, so you have to be careful to not to apply improper schema migrations.
If you are deploying simple services, maybe Django is overkill. For this use cases, use Flask or Sanic, as this are simpler and easier (and also faster) but you might have to live without all the Django goodies.
Rapid web development. Because it contains 95% of everything you need to develop any backend, you don't have to mix and match technologies and integrate them. This has a drawback: it is not always easy to integrate with other technologies.