Skip to content

Update wtforms to 2.3.1 - #67

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

Update wtforms to 2.3.1#67
pyup-bot wants to merge 1 commit into
masterfrom
pyup-update-wtforms-2.1-to-2.3.1

Conversation

@pyup-bot

Copy link
Copy Markdown
Collaborator

This PR updates WTForms from 2.1 to 2.3.1.

Changelog

2.3.0

-------------

Released 2020-04-21

-   Drop support for Python 2.6, 3.3, and 3.4.
-   :class:`~fields.SelectField` uses ``list()`` to construct a new list
 of choices. :pr:`475`
-   Permitted underscores in ``HostnameValidation``. :pr:`463`
-   :class:`~validators.URL` validator now allows query parameters in
 the URL. :issue:`523`, :pr:`524`
-   Updated ``false_values`` param in ``BooleanField`` docs.
 :issue:`483`, :pr:`485`
-   Fixed broken format string in Arabic translation :pr:`471`
-   Updated French and Japanese translations. :pr:`506, 514`
-   Updated Ukrainian translation. :pr:`433`
-   ``FieldList`` error list keeps entries in order for easier
 identification of which fields had errors. :issue:`257`, :pr:`407`
-   :class:`~validators.Length` gives a more helpful error message when
 ``min`` and ``max`` are the same value. :pr:`266`
-   :class:`~fields.SelectField` no longer coerces ``None`` to
 ``"None"`` allowing use of ``"None"`` as an option. :issue:`289`,
 :pr:`288`
-   The :class:`~widgets.TextArea` widget prepends a ``\r\n`` newline
 when rendering to account for browsers stripping an initial line for
 display. This does not affect the value. :issue:`238`, :pr:`395`
-   HTML5 :class:`~fields.html5.IntegerField` and
 :class:`~fields.html5.RangeInput` don't render the ``step="1"``
 attribute by default. :pr:`343`
-   ``aria_`` args are rendered the same way as ``data_`` args, by
 converting underscores to hyphens. ``aria_describedby="name-help"``
 becomes ``aria-describedby="name-help"``. :issue:`239`, :pr:`389`
-   Added a ``check_validators`` method to :class:`~fields.Field` which
 checks if the given validators are both callable, and not classes.
 :pr:`298, 410`
-   ``form.errors`` is not cached and will update if an error is
 appended to a field after access. :pr:`568`
-   :class:`~wtforms.validators.NumberRange` correctly handle NaN
 values. :issue:`505`, :pr:`548`
-   :class:`~fields.IntegerField` checks input type when processing
 data. :pr:`451`
-   Added a parameter to :class:`~fields.SelectField` to skip choice
 validation. :issue:`434`, :pr:`493`
-   Choices which name and data are the same do not need to use tuples.
 :pr:`526`
-   Added more documentation on HTML5 fields. :pr:`326, 409`
-   HTML is escaped using MarkupSafe instead of the previous internal
 implementation. :func:`~widgets.core.escape_html` is removed,
 replaced by :func:`markupsafe.escape`.
 :class:`~widgets.core.HTMLString` is removed, replaced by
 :class:`markupsafe.Markup`. :pr:`400`
-   Fixed broken IPv6 validator, validation now uses the ``ipaddress``
 package. :issue:`385`, :pr:`403`
-   :class:`~fields.core.Label` text is escaped before rendering.
 :issue:`315`, :pr:`375`
-   Email validation is now handled by an optional library,
 ``email_validator``. :pr:`429`

2.2.1

-------------

Released 2018-06-07

-   :class:`~fields.StringField` only sets ``data = ''`` when form data
 is empty and an initial value was not provided. This fixes an issue
 where the default value wasn't rendered with the initial form.
 :issue:`291, 401`, :pr:`355`

2.2

-----------

Released 2018-06-02

-   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``. :pr:`248`
-   The :class:`~validators.UUID` validator uses the :class:`uuid.UUID`
 class instead of a regex. :pr:`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. :pr:`286`
-   Fields call :meth:`~fields.Field.process_formdata` even if the raw
 data is empty. :pr:`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. :pr:`281`
-   :class:`~fields.SelectField` choices can contain HTML (MarkupSafe
 ``Markup`` object or equivalent API) and will be rendered properly.
 :pr:`302`
-   ``fields.TimeField`` and ``html5.TimeField`` were added. :pr:`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. :pr:`294`
-   Widgets render the ``required`` attribute when using a validator
 that provides the ``'required'`` flag, such as
 :class:`~validators.DataRequired`. :pr:`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``. :pr:`391`
Links

@pyup-bot pyup-bot mentioned this pull request Apr 22, 2020
@pyup-bot

Copy link
Copy Markdown
Collaborator Author

Closing this in favor of #73

@pyup-bot pyup-bot closed this Jul 30, 2020
@abdesslem
abdesslem deleted the pyup-update-wtforms-2.1-to-2.3.1 branch July 30, 2020 17:15
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