<commit_before>Differences with django.forms
=============================

So, you have a project already using django.forms, and you're considering a
switch to floppyforms? Here's what you need to know, assuming the only
change you've made to your code is a simple change, from:

.. code-block:: python

    from django import forms


to:

.. code-block:: python

    import floppyforms as forms

Standard forms
--------------

Floppyforms adds a couple of things on top of the standard django widgets:
HTML syntax, more native widget types, the ``required`` attribute and<commit_msg>Added a note so people don't fully consider floppyforms equivalent to django.forms<commit_after>Differences with django.forms
=============================

So, you have a project already using django.forms, and you're considering a
switch to floppyforms? Here's what you need to know, assuming the only
change you've made to your code is a simple change, from:

.. code-block:: python

    from django import forms


to:

.. code-block:: python

    import floppyforms as forms

.. note:: ``django.forms.*`` modules

    Other modules contained by ``django.forms``, such as ``forms``, ``utils``
    and ``formsets`` have not been aliased.

Standard forms
--------------

Floppyforms adds a couple of things on top of the standard django widgets:
HTML syntax, more native widget types, the ``required`` attribute and
{'fraction_non_alphanumeric': 0.13052781740370897, 'fraction_numerical': 0.0, 'mean_word_length': 3.9401408450704225, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3907456', 'n_tokens_mistral': 374, 'n_tokens_neox': 350, 'n_words': 180}