Re: subclassed ModelForms initial values behavior changed from 1.1beta to 1.1

2009-08-07 Thread Russell Keith-Magee
On Sat, Aug 8, 2009 at 10:17 AM, David Haas wrote: > > Fair enough.  I've got some style questions about the best way to do > what I want to do, but they're probably not so relevant here. > Something that might be relevant is this . . . is it worth submitting > a documentation patch for this issue

Re: subclassed ModelForms initial values behavior changed from 1.1beta to 1.1

2009-08-07 Thread David Haas
Fair enough. I've got some style questions about the best way to do what I want to do, but they're probably not so relevant here. Something that might be relevant is this . . . is it worth submitting a documentation patch for this issue? I was thinking something on this page: http://docs.django

Re: subclassed ModelForms initial values behavior changed from 1.1beta to 1.1

2009-08-04 Thread Malcolm Tredinnick
On Tue, 2009-08-04 at 22:23 +0800, Russell Keith-Magee wrote: > On Mon, Aug 3, 2009 at 3:46 AM, David Haas wrote: > > > > It looks like the change happened between rev. 10189 & 10190: 10189 > > displays the value, 10190 doesn't. > > > > Unfortunately, I don't think I can give you a completely unbi

Re: subclassed ModelForms initial values behavior changed from 1.1beta to 1.1

2009-08-04 Thread Russell Keith-Magee
On Mon, Aug 3, 2009 at 3:46 AM, David Haas wrote: > > It looks like the change happened between rev. 10189 & 10190: 10189 > displays the value, 10190 doesn't. > > Unfortunately, I don't think I can give you a completely unbiased > answer as to what behavior I think > is more correct, because of hi

Re: subclassed ModelForms initial values behavior changed from 1.1beta to 1.1

2009-08-02 Thread David Haas
It looks like the change happened between rev. 10189 & 10190: 10189 displays the value, 10190 doesn't. Unfortunately, I don't think I can give you a completely unbiased answer as to what behavior I think is more correct, because of history and personal use :) With that out on the table, though,

Re: subclassed ModelForms initial values behavior changed from 1.1beta to 1.1

2009-08-02 Thread Russell Keith-Magee
On Sun, Aug 2, 2009 at 12:58 PM, David Haas 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 ModelF

Re: subclassed ModelForms initial values behavior changed from 1.1beta to 1.1

2009-08-01 Thread David Haas
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 ini

Re: subclassed ModelForms initial values behavior changed from 1.1beta to 1.1

2009-08-01 Thread Ramiro Morales
On Sat, Aug 1, 2009 at 8:28 PM, David Haas wrote: > > Hi: > > I'm hoping to get some feedback on a little change in behavior I'm > seeing when initializing ModelForms between 1.1-beta & the official > 1.1 release. > > The quick and dirty explanation is this: I have a ModelForm which is a > subclas

subclassed ModelForms initial values behavior changed from 1.1beta to 1.1

2009-08-01 Thread David Haas
Hi: I'm hoping to get some feedback on a little change in behavior I'm seeing when initializing ModelForms between 1.1-beta & the official 1.1 release. The quick and dirty explanation is this: I have a ModelForm which is a subclass of another ModelForm. The parent ModelForm has the fields attri