Django 6.0 introduced AsyncPaginators, but as they made clear in ticket 36872, Django doesn’t want asynchronous methods used in DTLs; they simply prefer that they not be used at all.
Did they add AsyncPaginators just to address a specific API case where it doesn’t always work perfectly because asynchronous cursors aren’t implemented?
Welcome @rroblf01 !
The AsyncPaginator class was introduced as a result of ticket #35945 (Add async interface to Paginator) – Django
I don’t see any conversation here, in the google groups, the Django new features repo, or on Discord about this feature.
It was triaged and accepted back in Dec 2024, merged March 2025.
Aside from the comments in the original ticket, I can’t find any other conversation about it, so a reasonable assumption may be that it was implemented specifically to address the issue identified in that ticket.
Keep in mind that most of the code in Django is community-supplied. It’s not like there is a “Django Core Development” team working to add features.