Bump django-filter from 1.1 to 2.4.0 in /mooclet_engine

[dependabot]

Bumps django-filter from 1.1 to 2.4.0.

Release notes

Sourced from django-filter's releases.

Version 2.4.0

• SECURITY: Added a MaxValueValidator to the form field for NumberFilter. This prevents a potential DoS attack if numbers with very large exponents were subsequently converted to integers.

  The default limit value for the validator is 1e50.

  The new NumberFilter.get_max_validator() allows customising the used validator, and may return None to disable the validation entirely.

• Added testing against Django 3.1 and Python 3.9.

  In addition tests against Django main development branch are now required to pass.

Version 2.3.0

https://github.com/carltongibson/django-filter/blob/master/CHANGES.rst#version-230-2020-6-5

Version 2.2

Highlights:

• Added DjangoFilterBackend.get_schema_operation_parameters() for DRF 3.10+ OpenAPI schema generation. (#1086)
• Added lookup_expr to MultipleChoiceFilter (#1054)
• Dropped support for EOL Python 3.4

Version 2.1.0

• Fixed a regression in FilterView introduced in 2.0. An empty QuerySet was incorrectly used whenever the FilterSet was unbound (i.e. when there were no GET parameters). The correct, pre-2.0 behaviour is now restored.

  A workaround was to set strict=False on the FilterSet. This is no longer necessary, so you may restore strict behaviour as desired.

• Added IsoDateTimeFromToRangeFilter. Allows From-To filtering using ISO-8601 formatted dates.

Version 2.0

2.0 introduced a number of small changes and tidy-ups. Please see the migration guide:

https://django-filter.readthedocs.io/en/master/guide/migration.html#migrating-to-2-0

• Added testing for Python 3.7 (#944)
• Improve exception message for invalid filter result (#943)
• Test QueryDict against CSV filters (#937)
• Add renderer argument to render() method of BooleanWidget (#923)
• Fix lookups for reverse relationships (#915)
• Refactor backend filterset instantiation (#865)
• Improve view-related attribute name consistency (#867)

... (truncated)

Changelog

Sourced from django-filter's changelog.

Version 21.1 (2021-9-24)

This is a maintenance release updating CI testing for the latest non-end-of-life versions of Python and Django, and updating package metadata accordingly.

With this release django-filter is switching to a two-part CalVer versioning scheme, such as 21.1. The first number is the year. The second is the release number within that year.

On an on-going basis, Django-Filter aims to support all current Django versions, the matching current Python versions, and the latest version of Django REST Framework.

Please see:

• Status of supported Python branches <https://devguide.python.org/#status-of-python-branches>_
• List of supported Django versions <https://www.djangoproject.com/download/#support-versions>_

Support for Python and Django versions will be dropped when they reach end-of-life. Support for Python versions will dropped when they reach end-of-life, even when still supported by a current version of Django.

Other breaking changes are rare. Where required, every effort will be made to apply a "Year plus two" deprecation period. For example, a change initially introduced in 23.x would offer a fallback where feasible and finally be removed in 25.1. Where fallbacks are not feasible, breaking changes without deprecation will be called out in the release notes.

Beyond that change, there are few changes. Some small bugfixes, improvements to localisation, and documentation tweaks. Thanks to all who were involved.

Version 2.4.0 (2020-9-27)

• SECURITY: Added a MaxValueValidator to the form field for NumberFilter. This prevents a potential DoS attack if numbers with very large exponents were subsequently converted to integers.

  The default limit value for the validator is 1e50.

  The new NumberFilter.get_max_validator() allows customising the used validator, and may return None to disable the validation entirely.

• Added testing against Django 3.1 and Python 3.9.

  In addition tests against Django main development branch are now required to pass.

... (truncated)

Commits

• 7821072 Postpone move to CalVer.
• fd5824e Restore version declaration in setup.py.
• c9daa68 Version 20.9.0.
• c045bbe Droped using bumpversion.
• b1f56ed Use single version reference from main module.
• 451d372 Update docs copyright year.
• 82c9a42 Added MaxValueValidator to NumberFilter.
• 2ebce74 Confirmed compatibility with Python 3.9. (#1270)
• 85c9572 Run tests with GitHub Actions
• d9f389f Update Jinja test dependency.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.