> Adrian Holovaty Jan 13 12:07PM -0600
> The ultimate solution is: don't use model forms. I never use them for
> anything, precisely because of things like this, where the framework
> is trying to do too much behind the scenes. It's too magical for my
> tastes, and while I understand why we added
> The "ProfileForm({}, instance=profile)" is
> clearly passing in empty data (the empty dictionary), and it makes
> sense that Django would see the empty data, then determine that empty
> data is allowed on the fields (blank=True) and set those fields to
> empty data. If you want to avoid this, you
On Thu, Jan 12, 2012 at 7:40 PM, Tai Lee wrote:
> class Profile(models.Model):
> first_name = models.CharField(blank=True, max_length=50)
> last_name = models.CharField(blank=True, max_length=50)
> address = models.CharField(blank=True, max_length=50)
>
> class ProfileForm(ModelForm):
>
1. How does this proposal effect default values specified on model fields?
(ModelForm processing)
2. Forgive my ignorance but who has the final say if it goes in or not? And
since it should be a yes what's next?
On Thu, Jan 12, 2012 at 8:40 PM, Tai Lee wrote:
> Ian,
>
> I agree that there are a
