On Mar 1, 11:32 pm, Trevor Turk <
trevort...@gmail.com> wrote:
> If I don't hear any objections I'll try to work up a patch with doc
> fixes tomorrow and create a Lighthouse ticket.
I've done some research and added a new file to the original gist:
http://gist.github.com/70955
You're probably best off viewing it here:
http://gist.github.com/raw/70955/9ccc058386921fefcc9f9d3e6a9ca0b658619e63/gistfile2.txt
The upshot is that I feel changing the behavior of update_attribute
may have unexpected consequences, and I believe the short-term
solution may be to simply raise an exception if update_attribute is
given a readonly attribute.
This may be the easiest solution to implement, but it wouldn't have
the 100% desired effect (e.g. allowing update_attribute to work on a
readonly attribute). It would be low impact, though, and at least it
would notify the user that the action they're trying to take won't
work.
That way, at least the behavior would be clear. The fact that
update_attribute appears to work but doesn't actually work is the
"bug" in my mind. I'd prefer to make it actually work, but the options
I explored may end up being more problematic than are justified by the
issue at hand.
Thanks,
- Trevor