Thanks, that didn't show up in my search, but it's exactly the same
traceback.
The ticket description seems to indicate the bug only applies to
testing situations, but clearly it occurs in the default ModelForm
(and thereby in the admin) any time a foreign key is set to
null=False, blank=True. Leaving a field blank and filling it in in
the model's save() method seems to be a pretty common case, and I
would think should be allowed without creating a custom ModelForm.
Should this be listed somewhere as a backwards-incompatible change,
since it worked in 1.0?
On Jun 24, 6:22 pm, Karen Tracey <
kmtra...@gmail.com> wrote: