Bump django-crispy-forms from 1.12.0 to 2.0

[dependabot]

Bumps django-crispy-forms from 1.12.0 to 2.0.

Release notes

Sourced from django-crispy-forms's releases.

2.0 (2023-02-13)

Major Changes and Migration Guide

• Removed all Bootstrap template packs. These template packs are now available as standalone packages. To upgrade, install the required template pack and add it to your INSTALLED_APPS setting.

  • Boostrap 2: PyPI -- GitHub
  • Boostrap 3: PyPI -- GitHub
  • Boostrap 4: PyPI -- GitHub

  Also, support for Bootstrap 5 is provided by a 3rd party package under the django-crispy-forms organisation at crispy-bootstrap5.

• Removed uni-form template pack. Uni-Form specific classes previously added to every template pack e.g. textInput are now removed. If you require these classes, the previous behaviour can be restored by adding the following to CRISPY_CLASS_CONVERTERS in your settings file.

    converters = {
      "textinput": "textinput textInput",
      "fileinput": "fileinput fileUpload",
      "passwordinput": "textinput textInput",
  }
  

• The uni-form template pack allowed for rendering of templates using a default or inline layout. As the uni-form template pack has been removed support for this has also been removed. This has resulted in the following BREAKING changes.

  • The form_style attribute of FormHelper is removed.
  • The form_style positional argument to render_field() is removed.
  • The form_style positional argument to the render() method of all LayoutObjects is removed.

  Audit for use of render() and render_field() due to the removal of the form_style positional argument is therefore required. For example:

  # django-crispy-forms 1.x
  html = my_layout_object.render(form, form_style, context)
  # django-crispy-forms 2.x
  html = my_layout_object.render(form, context)
  

• Widespread use of the |safe in crispy-form templates is removed. Audit for html input in your forms especially for Field and Prepended/Appended text. To retain the previous behaviour mark text as safe in your project code using mark_safe(). Refs #296.

Other Changes

• Dropped support for Django 2.2.
• Added support for Django 4.1 and 4.2.

... (truncated)

Changelog

Sourced from django-crispy-forms's changelog.

2.0 (2023-03-13)

Release of django-crispy-forms 2.0. No changes introduced since 2.0a1.

2.0a1 (2023-01-18)

Major Changes and Migration Guide

• Removed all Bootstrap template packs. These template packs are now available as standalone packages. To upgrade, install the required template pack and add it to your INSTALLED_APPS setting.

  • Boostrap 2: PyPI -- GitHub
  • Boostrap 3: PyPI -- GitHub
  • Boostrap 4: PyPI -- GitHub

  Also, support for Bootstrap 5 is provided by a 3rd party package under the django-crispy-forms organisation at crispy-bootstrap5.

• Removed uni-form template pack. Uni-Form specific classes previously added to every template pack e.g. textInput are now removed. If you require these classes, the previous behaviour can be restored by adding the following to CRISPY_CLASS_CONVERTERS in your settings file.

    converters = {
      "textinput": "textinput textInput",
      "fileinput": "fileinput fileUpload",
      "passwordinput": "textinput textInput",
  }
  

• The uni-form template pack allowed for rendering of templates using a default or inline layout. As the uni-form template pack has been removed support for this has also been removed. This has resulted in the following BREAKING changes.

  • The form_style attribute of FormHelper is removed.
  • The form_style positional argument to render_field() is removed.
  • The form_style positional argument to the render() method of all LayoutObjects is removed.

  Audit for use of render() and render_field() due to the removal of the form_style positional argument is therefore required. For example:

  # django-crispy-forms 1.x
  html = my_layout_object.render(form, form_style, context)
  # django-crispy-forms 2.x
  html = my_layout_object.render(form, context)
  

• Widespread use of the |safe in crispy-form templates is removed. Audit for html input in your forms especially for Field and Prepended/Appended text. To retain the previous behaviour mark text as safe in your project code using mark_safe(). Refs #296.

... (truncated)

Commits

• a797499 2.0 Release (#1335)
• 447177d Drop Django 4.2 Classifier. (#1332)
• 60ca742 Pre-commit updates and Black 2023 style. (#1333)
• e958fef 2.0a1 release (#1294)
• 35c857c Added Django 4.2 support. (#1328)
• fedf64a Move project setup to pyproject.toml and build package with "build". (#1325)
• d8f0d34 Move pytest options to pyproject.toml (#1324)
• 40d4b48 Moved coverage config to pyproject.toml (#1323)
• fc8a568 Improved coverage of black linting. (#1322)
• b877144 Simplified flake8 config and moved to tox.ini (#1321)
• 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)