crispy forms must be so named because it's so brittle. meh.
actually, I can't blame it, the problem is that it's too closely tied to Django itself, which is a moving target. before 1.6, specifying __all__ for the fields attribute in a ModelForm would give the error django.core.exceptions.FieldError: Unknown field(s) (a, l, _) specified for CrispyTestModel, obviously casting the string to a set. and starting Django1.8, any ModelForm without either the fields or exclude attribute will raise an exception. so any package that wants to support a range of Python and Django releases has to have conditional code for this and many other similar changes. it's a mess.
Back to blog or home page
last updated 2015-04-03 02:31:16. served from tektonic