On Sun, Aug 2, 2009 at 12:58 PM, David Haas<david.h.h...@gmail.com> wrote: > > Ramiro: > > I've set up some models / forms / formsets which demonstrate the > change here: > > http://dpaste.de/YhrI/ > > My initial report wasn't correct - the change in behavior is only seen > when initalizing ModelFormSets . . . the ModelForm behavior is > unchanged. With a formset, the value use to get initialized; now it > doesn't. With a form, the value has never gotten initialized. > > I think 1.1 & 1.0.3 have the same behavior (no initialization in > formsets); and SVN 10132 (1.1 beta) & 1.0.2 have the same behavior > (initialization in formsets).
Hi David, Thanks for this report. I'll have to dig a bit deeper to see exactly what is going on here. If you want to help out, working out which changeset between 10132 (beta 1) and 11365 (1.1 final) introduced this discrepancy would be extremely helpful. I'd also be interested to hear which behaviour - history and personal uses notwithstanding - you think is correct. On first inspection, I'm not completely convinced that the 'new' behaviour is actually incorrect - or, at least, that there might be a larger bug lurking here with regard to the interpretation of inherited Meta.field arguments. However, this is entirely based on first impressions, late at night, with a mild headache, so I could be completely off base. Yours Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
