django-tables2 simplifies the task of turning sets of data into HTML tables. It has native support for pagination and sorting. It does for HTML tables what django.forms does for HTML forms. e.g.

Its features include:

• Any iterable can be a data-source, but special support for Django querysets is included.
• The builtin UI does not rely on JavaScript.
• Support for automatic table generation based on a Django model.
• Supports custom column functionality via subclassing.
• Pagination.
• Column based table sorting.
• Template tag to enable trivial rendering to HTML.
• Generic view mixin for use in Django 1.3.

Creating a table is as simple as:

import django_tables2 as tables

class SimpleTable(tables.Table):
    class Meta:
        model = Simple

This would then be used in a view:

def simple_list(request):
    queryset = Simple.objects.all()
    table = SimpleTable(queryset)
    return render_to_response("simple_list.html", {"table": table},
                              context_instance=RequestContext(request))

And finally in the template:

{% load django_tables2 %}
{% render_table table %}

This example shows one of the simplest cases, but django-tables2 can do a lot more! Check out the documentation for more details.

If you want to build the docs from within a virtualenv, and Sphinx is installed globally, use:

make html SPHINXBUILD="python $(which sphinx-build)"

• Fixed bug in render_table when giving it a template (issue #41)

• Added translation support in the default template via {% trans %}
• Removed basic_table.html, Table.as_html() now renders table.html but will clobber the querystring of the current request. Use the render_table template tag instead
• render_table now supports an optional second argument -- the template to use when rendering the table
• Table now supports declaring which template to use when rendering to HTML
• Django >=1.3 is now required
• Added support for using django-haystack's SearchQuerySet as a data source
• The default template table.html now includes block tags to make it easy to extend to change small pieces
• Fixed table template parsing problems being hidden due to a subsequent exception being raised
• Http404 exceptions are no longer raised during a call to Table.paginate(), instead it now occurs when Table.page is accessed
• Fixed bug where a table couldn't be rendered more than once if it was paginated
• Accessing Table.page now returns a new page every time, rather than reusing a single object

• Tables now support using both sequence and exclude (issue #32).
• Sequence class moved to django_tables2/utils.py.
• Table instances now support modification to the exclude property.
• Removed BoundColumns._spawn_columns.
• Table.data, Table.rows, and Table.columns are now attributes rather than properties.