On Thu, 2007-07-05 at 10:52 +0300, Noam Raphael wrote: > On 7/5/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > It's a backwards-incompatible change, so we'd need a strong reason to > > change it. > [...] > > This line of reasoning is unfortunately not particularly strong. The > > problem is that one group of people might find the current behaviour of > > something unintuitive. Another group might find the alternative verion > > unintuitive and then there's no resolution. > > This is hypothetical. Do you have an example, or can you think of a > situation, in which someone will set the field to some value and rely > on Django to reset it to the current date?
Form submission data for a form class created by form_for_model(). [...] > 2. This isn't really backwards-incompatible, since there is no real > code that depends on the current behaviour. There are thousands of users of Django. A claim like that is very hard to make. [...] > > In this particular case, I'll point out that the behaviour of > > auto_now_add is clearly documented. It says that it is not a default you > > can override. Similarly for auto_now. > > Well, I didn't read it, and it was counter-intuitive to me. I spend an > hour or more on debugging, and, as I said, I don't think I'm > especially stupid. I also don't think that users should be expected to > read the entire documentation before using Django. You're not being asked to read the entire documentation. You did have to read the models API to learn that auto_now_add existed in the first place. It is not really unreasonable to think that if somebody is having trouble making auto_now_add work, they will fairly quickly check the docs to make sure they are using it correctly. It's hardly an unusual work pattern that if something new you are doing does not work as expected, you check your assumptions. Best wishes, Malcolm -- I just got lost in thought. It was unfamiliar territory. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
