Skip to content

Update wtforms to 2.2.1 - #15

Closed
pyup-bot wants to merge 1 commit into
masterfrom
pyup-update-wtforms-2.1-to-2.2.1
Closed

Update wtforms to 2.2.1#15
pyup-bot wants to merge 1 commit into
masterfrom
pyup-update-wtforms-2.1-to-2.2.1

Conversation

@pyup-bot

@pyup-bot pyup-bot commented Jun 7, 2018

Copy link
Copy Markdown
Collaborator

This PR updates WTForms from 2.1 to 2.2.1.

Changelog

2.2

-----------

Released June 2nd, 2018

-   Merged new and updated translations from the community.
-   Passing ``data_`` args to render a field converts all the
 underscores to hyphens when rendering the HTML attribute, not just
 the first one. ``data_foo_bar`` becomes ``data-foo-bar``. (`248`_)
-   The :class:`~validators.UUID` validator uses the :class:`uuid.UUID`
 class instead of a regex. (`251`_)
-   :class:`~fields.SelectField` copies the list of ``choices`` passed
 to it so modifying an instance's choices will not modify the global
 form definition. (`286`_)
-   Fields call :meth:`~fields.Field.process_formdata` even if the raw
 data is empty. This makes :class:`~fields.StringField` default to an
 empty string instead of ``None``. (`280`_)
-   Added a :class:`~fields.MultipleFileField` to handle a multi-file
 input. :class:`~fields.FileField` continues to handle only one
 value. The underlying :class:`~widgets.FileInput` widget gained a
 ``multiple`` argument. (`281`_)
-   :class:`~fields.SelectField` choices can contain HTML (MarkupSafe
 ``Markup`` object or equivalent API) and will be rendered properly.
 (`302`_)
-   :class:`~fields.TimeField` and
 :class:`html5.TimeField <fields.html5.TimeField>` were added.
 (`254`_)
-   Improved :class:`~validators.Email`. Note that it is still
 unreasonable to validate all emails with a regex and you should
 prefer validating by actually sending an email. (`294`_)
-   Widgets render the ``required`` attribute when using a validator
 that provides the ``'required'`` flag, such as
 :class:`~validators.DataRequired`. (`361`_)
-   Fix a compatibility issue with SQLAlchemy 2.1 that caused
 :class:`~ext.sqlalchemy.fields.QuerySelectField` to fail with
 ``ValueError: too many values to unpack``. (`391`_)

.. _248: https://github.com/wtforms/wtforms/pull/248
.. _251: https://github.com/wtforms/wtforms/pull/251
.. _254: https://github.com/wtforms/wtforms/pull/254
.. _280: https://github.com/wtforms/wtforms/pull/280
.. _281: https://github.com/wtforms/wtforms/pull/281
.. _286: https://github.com/wtforms/wtforms/pull/286
.. _294: https://github.com/wtforms/wtforms/pull/294
.. _302: https://github.com/wtforms/wtforms/pull/302
.. _361: https://github.com/wtforms/wtforms/pull/361
.. _391: https://github.com/wtforms/wtforms/pull/391
Links

@pyup-bot pyup-bot mentioned this pull request Jun 7, 2018
@pyup-bot

Copy link
Copy Markdown
Collaborator Author

Closing this in favor of #66

@pyup-bot pyup-bot closed this Apr 21, 2020
@abdesslem
abdesslem deleted the pyup-update-wtforms-2.1-to-2.2.1 branch April 21, 2020 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant