[1.6.x] Added release note for TypedChoiceField coerce limitation

Thanks Elec for the report and Simon Charette for the review.
Refs #21397.
Backport of 4a00f132e0 from master.
This commit is contained in:
Claude Paroz 2013-11-18 18:06:57 +01:00
parent a9c50fccf2
commit 9f59149cfe
1 changed files with 5 additions and 0 deletions

View File

@ -873,6 +873,11 @@ Miscellaneous
:class:`~django.forms.SlugField` have been suppressed because they :class:`~django.forms.SlugField` have been suppressed because they
duplicated error messages already provided by validators tied to the fields. duplicated error messages already provided by validators tied to the fields.
* Due to a change in the form validation workflow,
:class:`~django.forms.TypedChoiceField` ``coerce`` method should always
return a value present in the ``choices`` field attribute. That limitation
should be lift again in Django 1.7.
* There have been changes in the way timeouts are handled in cache backends. * There have been changes in the way timeouts are handled in cache backends.
Explicitly passing in ``timeout=None`` no longer results in using the Explicitly passing in ``timeout=None`` no longer results in using the
default timeout. It will now set a non-expiring timeout. Passing 0 into the default timeout. It will now set a non-expiring timeout. Passing 0 into the