On 12.02.2010 13:39, Russell Keith-Magee wrote: > > Hopefully that clarifies why Django works the way it does.
Yes, it does. Thank you, Russel. > However, > even if, hypothetically, we were to accept that Django's current > behavior is in error, (...) there is an enormous issue of practicality. > (...) > Although the > change would be a minor code modification, it would be *very* > complicated to change it in practice, given Django's API backwards > compatibility guarantee. And as a result, we're *not* going to change > it. Yes, this is a good reason to not change Django's behaviour, independently of whether it is "wrong" or not. Luc -- 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.
