Django-filter

Latest version: v24.3

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

Scan your dependencies

Page 5 of 7

0.15.0

Not secure
---------------------------

This is a preparatory release for a 1.0. Lots of clean-up, lots of changes,
mostly backwards compatible.

Special thanks to Ryan P Kilby (rpkilby) for lots of hard work.

Most changes should raise a Deprecation Warning.

**Note**: if you're doing *Clever Things™* with the various filter options
— ``filter_overrides`` etc — you may run into an `AttributeError` since these
are now defined on the metaclass and not on the filter itself.
(See the discussion on 459)

Summary: Highly Recommended, but take a moment to ensure everything still works.

* Added the DRF backend. 481

* Deprecated `MethodFilter` in favour of `Filter.method` 382

* Move filter options to metaclass 459

* Added `get_filter_predicate` hook. (Allows e.g. filtering on annotated fields) 469

* Rework Ordering options into a filter 472

* Hardened all deprecations for 1.0. Please do see the `Migration Notes`__

__ https://github.com/carltongibson/django-filter/blob/1.0.0/docs/guide/migration.txt

0.14.0

Not secure
---------------------------

* Confirmed support for Django 1.10.

* Add support for filtering on DurationField (new in Django 1.8).

* Fix UUIDFilter import issue

* Improve FieldLookupError message

* Add filters_for_model to improve extensibility

* Fix limit_choices_to behavior with callables

* Fix distinct behavior for range filters

* Various Minor Clean up issues.

0.13.0

Not secure
---------------------------

* Add support for filtering by CSV 363

* Add DateTimeFromToRangeFilter 376

* Add Chinese translation 359

* Lots of fixes.

0.12.0

Not secure
---------------------------

* Raised minimum Django version to 1.8.x

* FEATURE: Add support for custom ORM lookup types 221

* FEATURE: Add JavaScript friendly BooleanWidget 270

* FIXED: (More) Compatability with Django 1.8 and Django 1.9+

* BREAKING CHANGE: custom filter names are now also be used for ordering 230

If you use ordering on a field you defined as custom filter with custom
name, you should now use the filter name as ordering key as well.

Eg. For a filter like :

class F(FilterSet):
account = CharFilter(name='username')
class Meta:
model = User
fields = ['account', 'status']
order_by = True

Before, ordering was like `?o=username`. Since 0.12.0 it's `o=account`.

0.11.0

Not secure
---------------------------

* FEATURE: Added default filter method lookup for MethodFilter 222

* FEATURE: Added support for yesterday in daterangefilter 234

* FEATURE: Created Filter for NumericRange. 236

* FEATURE: Added Date/time range filters 215

* FEATURE: Added option to raise with `strict` 255

* FEATURE: Added Form Field and Filter to parse ISO-8601 timestamps

0.10.0

Not secure
---------------------

* FEATURE: Added ``conjoined`` parameter to ``MultipleChoiceFilter``

* FEATURE: Added ``together`` meta option to validate fields as a group

* FIXED: Added testing on Django 1.8

* FIXED: ``get_model_field`` on Django 1.8

Page 5 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.