Maybe I should mention: Since only specially decorated views act this way, the change is completely backwards-compatible. At its current state, it does restrict how you use "internal" and "format" as capturing patterns in URLs, obviously.
Also, the format-decorator checks if the view returns a HttpResponse and if so, returns that directly. This is for the sake of supporting HttpResponseRedirect. An interesting effect of this whole thing is that it decouples views from not only formatting but protocol. Further generalized, they might raise NotFound-exceptions rather than Http404. A higher level mechanism would know how we're communicating with the user and make sure the right 'language' is spoken. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
