WTForms 3.2.1__tar.gz → 3.3.0__tar.gz

{wtforms-3.2.1 → wtforms-3.3.0}/.gitignore

@@ -15,3 +15,4 @@ __pycache__/
 /htmlcov/
 /docs/_build/
 /src/wtforms/locale/**/wtforms.mo
+uv.lock

{wtforms-3.2.1 → wtforms-3.3.0}/CHANGES.rst

@@ -1,5 +1,125 @@
 .. currentmodule:: wtforms
 
+Version 3.3.0
+-------------
+
+Released 2026-10-23
+
+- Drop support for Python 3.10. Add support for Python 3.15.
+- Add native :class:`DataList` support. Options are declared with
+  :class:`DataListChoice`, or with the shorthand ``{value: label}``
+  dict syntax. :issue:`653` :issue:`886` :pr:`921`
+- Add :class:`~fields.ButtonField` to render ``<button type="submit">``
+  controls with string values. :issue:`784` :pr:`892`
+- Add :class:`~validators.DateRange`. ``min`` and ``max`` may be callables
+  to compute dynamic bounds; :class:`~validators.NumberRange` accepts
+  callables on the same terms. :pr:`787`
+- Add :class:`~fields.FieldList` ``insert_entry`` and indexed ``pop_entry``.
+  The following entries are renumbered, with their ids and labels.
+  :issue:`256` :pr:`901` :pr:`912`
+- :class:`~fields.SelectField` refactor. Options are declared with
+  :class:`~fields.SelectChoice`, which takes HTML attributes in
+  ``render_kw`` and an ``optgroup``. ``iter_choices``
+  and ``iter_groups`` yield
+  :class:`~fields.Choice` objects. ``choices`` also accepts the shorthand
+  dict syntax: ``{value: label}`` for flat options and
+  ``{label: {value: label}}`` for optgroups. :issue:`692` :issue:`886`
+  :issue:`922` :pr:`739` :pr:`889`
+- ``choices`` callables on :class:`~fields.SelectField` and
+  :class:`DataList` may accept ``(form, field)``. They run on the
+  first read and their result is cached. Calling
+  :meth:`~form.BaseForm.post_process` again refreshes them, also for the
+  entries added with :meth:`~fields.FieldList.append_entry` and
+  :meth:`~fields.FieldList.insert_entry`. :issue:`922`
+- Add :func:`fields.enum_choices`, :func:`fields.enum_coerce` and
+  :func:`~datalist.enum_datalist` for Enum-backed choices. :issue:`338`
+  :issue:`922` :pr:`916`
+- Add :meth:`fields.Field.post_process` and
+  :meth:`form.BaseForm.post_process` hooks, propagated through
+  :class:`~fields.FormField` and :class:`~fields.FieldList`, for
+  cross-field finalization. :issue:`922`
+- Add ``Field._form`` and ``BaseForm._parent_form`` so fields and nested
+  forms can reach their enclosing form. :class:`~fields.FieldList` entries
+  and :class:`~fields.SelectField` option subfields no longer get
+  ``form=None``. :issue:`922`
+- Add ``invalid_value_message`` and ``invalid_choice_message`` keyword
+  arguments for customizing built-in field error messages. On
+  :class:`~fields.SelectMultipleField`, ``invalid_choice_message`` may also
+  be a callable for custom pluralization. :issue:`39` :issue:`832` :pr:`902`
+- :class:`~fields.SelectField` and :class:`~fields.SelectMultipleField`
+  ``pre_validate`` short-circuits when ``process_formdata`` already produced
+  an error, so a single coercion failure no longer surfaces as both an
+  "invalid value" and an "invalid choice" error. :pr:`902`
+- Numeric, date, time and select fields report a validation error instead of
+  raising a :class:`TypeError` when the input is not a string. :pr:`936`
+- Each bound field gets its own copy of ``render_kw``, and so does its
+  :class:`DataList`. Changing one of them on a form instance no
+  longer changes it on the other ones. :issue:`942`
+- Make :class:`~fields.FloatField` render as ``<input type="number">`` with
+  ``step="any"``. :issue:`677` :pr:`679`
+- Add a ``tz`` parameter to :class:`~fields.DateTimeLocalField` to associate a
+  timezone with the input. :issue:`833` :pr:`905`
+- Let :class:`~widgets.RangeInput` accept ``min`` and ``max`` at construction
+  time. :issue:`693` :pr:`898`
+- ``FieldList._add_entry`` routes through
+  :meth:`~meta.DefaultMeta.bind_field`, like the top-level fields. Custom
+  ``Meta.bind_field`` overrides were silently bypassed for
+  :class:`~fields.FieldList` entries. :pr:`891`
+- Reset :class:`~fields.FieldList` index state when reprocessing entries.
+  :issue:`874` :pr:`895`
+- Do not render a ``for`` attribute on the main label of
+  :class:`~fields.RadioField`. :issue:`775` :pr:`900`
+- Render ``False`` as ``value="False"`` in :class:`~fields.SelectField`
+  options instead of omitting the attribute. :issue:`878` :pr:`908`
+- Let render-time ``checked`` kwargs take precedence over the field's value
+  in :class:`~widgets.CheckboxInput` and :class:`~widgets.RadioInput`.
+  :issue:`706` :pr:`910`
+- Escape double quotes in ``Markup`` attribute values
+  passed to :func:`~widgets.html_params`, and return a
+  ``Markup``. :issue:`801` :pr:`906` :pr:`907`
+- Add ``test_environment`` support to :class:`~validators.Email`, and defer
+  to ``email_validator``'s module-level defaults for its
+  ``test_environment``, ``allow_smtputf8`` and ``allow_empty_local``
+  options. :issue:`869` :issue:`915` :pr:`894` :pr:`917`
+- Add ``matcher`` and ``html_pattern`` keyword arguments to
+  :class:`~validators.Regexp`. ``matcher`` overrides the matching function,
+  :func:`re.match` by default: pass :func:`re.search` or :func:`re.fullmatch`
+  to change the anchoring. ``html_pattern`` controls the HTML ``pattern``
+  attribute emitted on supporting widgets. :issue:`867` :pr:`759` :pr:`918`
+- :class:`~validators.URL` validator is based on ``urllib.parse.urlparse``
+  instead of a regex. New keyword arguments: ``allow_userinfo`` for
+  accepting ``user:password@host`` URLs; ``schemes``
+  (default ``("http", "https")``) is the allowlist of accepted schemes.
+  :pr:`847`
+- Accept :class:`uuid.UUID` instances in the :class:`~validators.UUID`
+  validator, and translate unexpected types into
+  :class:`~validators.ValidationError` instead of letting
+  :class:`TypeError` escape. :issue:`549` :pr:`769`
+- Clarify the documentation of filters, and of :class:`~fields.SelectField`
+  ``choices``. :issue:`859` :issue:`875` :pr:`896` :pr:`909`
+- Update the Dutch and Serbian translations.
+- Deprecate :class:`~fields.DateTimeField`, which will be removed in WTForms
+  3.4. :issue:`831` :pr:`897`
+- Passing :class:`~fields.SelectField` ``choices`` as tuples, or as a dict
+  that is not the shorthand syntax, is deprecated and will be removed in
+  WTForms 3.4. Use :class:`~fields.SelectChoice` instead. :issue:`922`
+- Passing a callable to ``SelectFieldBase._choices_from_input`` is
+  deprecated and will be removed in WTForms 3.4.
+- For :class:`~fields.SelectField` subclasses, yielding raw tuples from
+  ``iter_choices`` or
+  ``iter_groups``, and overriding
+  ``Select.render_option`` with the pre-3.3 signature, are
+  deprecated and will be removed in WTForms 4.0. :issue:`922`
+
+Version 3.2.2
+-------------
+
+Released 2026-05-03
+
+- Fix :class:`~validators.Disabled` validation with provided formdata. :pr:`880`
+- End support for Python 3.9, start support for Python 3.14. :pr:`883`
+- Add Tamil and Serbian translations.
+
 Version 3.2.1
 -------------
 
@@ -35,7 +155,6 @@ Released 2024-10-20
    If you need to keep the old behavior you can set the ``_form_error_key``
    parameter of your form to :data:`None`.
 
-
 Version 3.1.2
 -------------
 

{wtforms-3.2.1 → wtforms-3.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.3
+Metadata-Version: 2.5
 Name: WTForms
-Version: 3.2.1
+Version: 3.3.0
 Summary: Form validation and rendering for Python web development.
 Project-URL: Documentation, https://wtforms.readthedocs.io
 Project-URL: Changes, https://wtforms.readthedocs.io/changes
@@ -44,10 +44,10 @@ Classifier: License :: OSI Approved :: BSD License
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python
 Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
-Requires-Python: >=3.9
-Requires-Dist: markupsafe
+Requires-Python: >=3.11
+Requires-Dist: markupsafe>=1.1.1
 Provides-Extra: email
-Requires-Dist: email-validator; extra == 'email'
+Requires-Dist: email-validator>=2.0; extra == 'email'
 Description-Content-Type: text/x-rst
 
 WTForms
@@ -86,11 +86,6 @@ with frameworks even better.
     validators.
 -   `WTForms-SQLAlchemy`_ provides ORM-backed fields and form generation
     from SQLAlchemy models.
--   `WTForms-AppEngine`_ provides ORM-backed fields and form generation
-    from AppEnding db/ndb schema
--   `WTForms-Django`_ provides ORM-backed fields and form generation
-    from Django models, as well as integration with Django's I18N
-    support.
 -   `WTForms-Bootstrap5`_ provides Bootstrap 5 favor renderer with
     great customizability.
 -   `Starlette-WTF`_ integrates with Starlette and the FastAPI
@@ -101,8 +96,6 @@ with frameworks even better.
 .. _Flask-WTF: https://flask-wtf.readthedocs.io/
 .. _WTForms-Alchemy: https://wtforms-alchemy.readthedocs.io/
 .. _WTForms-SQLAlchemy: https://github.com/pallets-eco/wtforms-sqlalchemy
-.. _WTForms-AppEngine: https://github.com/pallets-eco/wtforms-appengine
-.. _WTForms-Django: https://github.com/pallets-eco/wtforms-django
 .. _WTForms-Bootstrap5: https://github.com/LaunchPlatform/wtforms-bootstrap5
 .. _Starlette-WTF: https://github.com/muicss/starlette-wtf
 .. _Bootstrap-Flask: https://github.com/helloflask/bootstrap-flask

{wtforms-3.2.1 → wtforms-3.3.0}/README.rst

@@ -34,11 +34,6 @@ with frameworks even better.
     validators.
 -   `WTForms-SQLAlchemy`_ provides ORM-backed fields and form generation
     from SQLAlchemy models.
--   `WTForms-AppEngine`_ provides ORM-backed fields and form generation
-    from AppEnding db/ndb schema
--   `WTForms-Django`_ provides ORM-backed fields and form generation
-    from Django models, as well as integration with Django's I18N
-    support.
 -   `WTForms-Bootstrap5`_ provides Bootstrap 5 favor renderer with
     great customizability.
 -   `Starlette-WTF`_ integrates with Starlette and the FastAPI
@@ -49,8 +44,6 @@ with frameworks even better.
 .. _Flask-WTF: https://flask-wtf.readthedocs.io/
 .. _WTForms-Alchemy: https://wtforms-alchemy.readthedocs.io/
 .. _WTForms-SQLAlchemy: https://github.com/pallets-eco/wtforms-sqlalchemy
-.. _WTForms-AppEngine: https://github.com/pallets-eco/wtforms-appengine
-.. _WTForms-Django: https://github.com/pallets-eco/wtforms-django
 .. _WTForms-Bootstrap5: https://github.com/LaunchPlatform/wtforms-bootstrap5
 .. _Starlette-WTF: https://github.com/muicss/starlette-wtf
 .. _Bootstrap-Flask: https://github.com/helloflask/bootstrap-flask

{wtforms-3.2.1 → wtforms-3.3.0}/docs/conf.py

@@ -13,6 +13,7 @@ release, version = get_version("WTForms")
 master_doc = "index"
 extensions = [
     "sphinx.ext.autodoc",
+    "sphinx.ext.extlinks",
     "sphinx.ext.intersphinx",
     "sphinx.ext.viewcode",
     "pallets_sphinx_themes",
@@ -22,6 +23,20 @@ extensions = [
 intersphinx_mapping = {
     "python": ("https://docs.python.org/3/", None),
 }
+extlinks = {
+    "mdn-tag": (
+        "https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/%s",
+        "<%s>",
+    ),
+    "mdn-attr": (
+        "https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/%s",
+        "%s",
+    ),
+    "mdn-input": (
+        "https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input/%s",
+        '<input type="%s">',
+    ),
+}
 issues_github_path = "pallets-eco/wtforms"
 
 # HTML -----------------------------------------------------------------

{wtforms-3.2.1 → wtforms-3.3.0}/docs/crash_course.rst

@@ -133,6 +133,22 @@ providing with data. Typically, you will want to assign the values manually, but
 for this simple case it's perfect. It can also be useful for CRUD and admin
 forms.
 
+The same pattern extends to a collection of objects: a
+:class:`~wtforms.fields.FormField` describes one item, a
+:class:`~wtforms.fields.FieldList` holds the list, and ``obj`` /
+``populate_obj`` thread through both ends::
+
+    class ItemForm(Form):
+        name     = StringField()
+        quantity = IntegerField()
+
+    class CartForm(Form):
+        items = FieldList(FormField(ItemForm))
+
+    form = CartForm(request.form, obj=cart)  # cart.items == [item1, item2, ...]
+    if form.validate():
+        form.populate_obj(cart)
+
 
 Exploring in the console
 ^^^^^^^^^^^^^^^^^^^^^^^^

{wtforms-3.2.1 → wtforms-3.3.0}/docs/faq.rst

@@ -57,7 +57,7 @@ you should have no unicode issues.
 What versions of Python are supported?
 --------------------------------------
 
-WTForms supports Python 3.9+
+WTForms supports Python 3.10+
 
 
 How can I contribute to WTForms?