Django-tables2

Latest version: v2.7.0

Safety actively analyzes 688931 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 18 of 20

0.9.6

- Fix bug that caused an ordered column's `<th>` to have no HTML attributes.

0.9.5

- Updated example project to add `colspan` on footer cell so table border renders correctly in Webkit.
- Fix regression that caused 'sortable' class on <th>.
- `Table.__init__` no longer *always* calls `.order_by()` on QuerySets, fixes 55.
This does introduce a slight backwards incompatibility. `Table.order_by` now has the possibility of returning `None`, previously it would *always* return an `OrderByTuple`.
- `DeclarativeColumnsMetaclass.__new__` now uses `super()``
- Testing now requires pylint and Attest >=0.5.3

0.9.4

- Fix regression that caused column verbose_name values that were marked as
safe to be escaped. Now any verbose_name values that are instances of
SafeData are used unmodified.

0.9.3

- Fix regression in `SingleTableMixin`.
- Remove stray `print` statement.

0.9.2

- `SingleTableView` now uses `RequestConfig`. This fixes issues with
`order_by_field`, `page_field`, and `per_page_field` not being honored.
- Add `Table.Meta.per_page` and change `Table.paginate` to use it as default.
- Add `title` template filter. It differs from Django's built-in `title` filter
because it operates on an individual word basis and leaves words containing
capitals untouched. **Warning**: use `{% load ... from ... %}` to avoid
inadvertently replacing Django's built-in `title` template filter.
- `BoundColumn.verbose_name` no longer does `capfirst`, capitalizing is now the
responsibility of `Column.header`.
- `BoundColumn.__unicode__` now uses `BoundColumn.header` rather than
`BoundColumn.verbose_name`.

0.9.1

- Fix version in `setup.py`

Page 18 of 20

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.