chango.git - django

Age	Commit message (Collapse)	Author
2013-08-15	[1.6.x] Fixed #20895 -- Made check management command warn if a BooleanField ↵	Alasdair Nicol
	does not have a default value Thanks to Collin Anderson for the suggestion and Tim Graham for reviewing the patch. Backport of 22c6497f99 from master
2013-07-19	[1.6.x] Fixed #20765 -- Set small values of `step` using exponential notation.	Simon Charette
	Browsers parse small factors of 10 as 0 under decimal notation. Thanks to Trac alias matklad for the report and Claude Paroz for the review. Backport of 415a36947c from master.
2013-07-01	[1.6.x] Fixed a couple form/formset deprecation warnings in tests.	Tim Graham
	Backport of a521d10322 from master.
2013-06-22	Fixed 17478 -- Allowed queryset overriding in BaseModelFormSet init	Claude Paroz
	BaseModelFormSet.forms is now a cached property instead of being populated in the __init__ method. This behaviour also matches an example in the documentation. Thanks Thomasz Swiderski for the report and Simon Charette for the review.
2013-06-20	Fixed #20630 -- Removed `maxlength` attribute from `NumberInput`.	Simon Charette
	This attribute is only allowed on inputs of type "text", "search", "url", "tel", "email", or "password". Thanks to yoyoma for the report and @bmispelon for the review.
2013-06-13	Fixed #20000 -- Allowed ModelForm meta overrides for label, help_text and ↵	Loic Bistuer
	error_messages
2013-05-09	Fixed #19733 - deprecated ModelForms without 'fields' or 'exclude', and ↵	Luke Plant
	added '__all__' shortcut This also updates all dependent functionality, including modelform_factory and modelformset_factory, and the generic views `ModelFormMixin`, `CreateView` and `UpdateView` which gain a new `fields` attribute.
2013-03-21	Fixed #20084 -- Provided option to validate formset max_num on server.	Andrew Gorcester
	This is provided as a new "validate_max" formset_factory option defaulting to False, since the non-validating behavior of max_num is longstanding, and there is certainly code relying on it. (In fact, even the Django admin relies on it for the case where there are more existing inlines than the given max_num). It may be that at some point we want to deprecate validate_max=False and eventually remove the option, but this commit takes no steps in that direction. This also fixes the DoS-prevention absolute_max enforcement so that it causes a form validation error rather than an IndexError, and ensures that absolute_max is always 1000 more than max_num, to prevent surprising changes in behavior with max_num close to absolute_max. Lastly, this commit fixes the previous inconsistency between a regular formset and a model formset in the precedence of max_num and initial data. Previously in a regular formset, if the provided initial data was longer than max_num, it was truncated; in a model formset, all initial forms would be displayed regardless of max_num. Now regular formsets are the same as model formsets; all initial forms are displayed, even if more than max_num. (But if validate_max is True, submitting these forms will result in a "too many forms" validation error!) This combination of behaviors was chosen to keep the max_num validation simple and consistent, and avoid silent data loss due to truncation of initial data. Thanks to Preston for discussion of the design choices.
2013-03-01	Fixed #18898 -- Added tests with a fix for ModelMultipleChoiceField	Claude Paroz

2013-02-26	Merged regressiontests and modeltests into the test root.	Florian Apolloner