siuba VS django-tables2

I don't know what's best for you, but I can recommend Siuba, a tidy interface for Python to send queries to pandas and SQL-db.

You mean siuba?

For further inspiration, this is a pretty good-looking "dplyr for Python": https://github.com/machow/siuba

You should follow /u/the75th's advice. However, if you decide to buck that take, I'd look into siuba. I've never heard of those packages you've listed, and have doubts they'd be maintained.

Check out siuba

How does this compare to https://github.com/jieter/django-tables2? That one makes it really easy to display database models with column sorting and pagination.

The degree of reusability (Thanks to things like GenericForeignKey and the ubiquity of Django Templates and Django ORM, there are tons of reusable components like django-filter or django-tables)

In Django there is django-tables2 for example, that creates html table from database query.

(eg. "Django apps" like django-filter and django-tables2, which rely on being a slice across the ORM, controller layer, and templating engine.)

From the readthedocs tutorial, A few examples:

I don't see how Axum would enable something like django-tables2 or django-filter which has is vertically integrated with Django's ORM, routing layer, and template system.

I've used actix-web for stuff... but I'm just sick of constantly reinventing the rote boilerplate that things like django-tables2 and django-filter generate for me once I've declared whatever customizations I want.

django-tables2 - like crispy forms but for tables, abstracts away the need to render tables in a template.