Re: field cannot be specified for model form as it is a non-editable field

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