Yep, that looks like it. IMHO, this is a bug that should be fixed without delay, as it breaks a cardinal rule for Pythonistas, and could even lead to a "data corruption" situation, if a dev was to add a boolean field and forget to update a form or fixture, or both.
On Monday, September 24, 2012 5:44:29 AM UTC-4, Aymeric Augustin wrote: > > 2012/9/24 Yo-Yo Ma <[email protected] <javascript:>> > >> This may be the intended behavior, but I couldn't find docs on it. My >> recommendation would defer to "The Zen of Python" >> >> In the face of ambiguity, refuse the temptation to guess. >> >> I would rather see the typical IntegrityError: Problem installing >> fixture... > > > Hello, > > This looks a lot like: https://code.djangoproject.com/ticket/15124 > > I hope I'll have time to study this problem again before the feature > freeze of 1.5. > > -- > Aymeric. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/6i5BdRrk8y0J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
