If you have a patch in mind, I'll take a look, however, considering there's talk of deprecating those options [0] in favor the alternatives that the docs mentioned, I don't think we should spend much time reconsidering their semantics.
[0] https://code.djangoproject.com/ticket/22995 On Monday, May 8, 2017 at 10:47:25 AM UTC-4, Melvyn Sopacua wrote: > > On Monday 08 May 2017 04:07:09 Tim Graham wrote: > > > > > > > The change to raise FieldError for non-editable fields was meant to > > > prevent bugs, not to block devs from doing what they want. > > > > But auto_now_add without auto_now is not a reason to make the field > non-editable. I should be able to use it in a model form, since the update > case is unhandled. > > > > However, this has always (at least 1.8.x and up) been the case for the > field and as you say, it now exposes a bug. > > -- > > Melvyn Sopacua > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/041adad9-2b1d-4076-a192-cbd923b8b18e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
