Waylan: > Therefore, don't use Person.objects.create()!!!! Marty: > Developer mistakes can ruin your data. Full stop.
> Unfortunately, this is one of the many issues where "X doesn't work > the way I think it should" gets confused with "X doesn't work the way > it should" or even "X doesn't work." If you have a constructive > argument for how you think it should work that can be implemented in a > way that doesn't break compatibility with other people's code, feel > free to propose that and discuss it. But spinning around about how > "wrong" the behavior is currently doesn't help anybody. What's with all the hostility here? I've heard about this from others. > ...constructive argument... Your thesis about the semantics of suggesting features is more constructive? Suggesting an idea here gets you just about the same as joining an elementary school hide-and-go-seek game and trying to change the rules. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
