Yuri, I am with you.
I am new to Django and am deep in the middle of my first major project using Django. When I encountered get_absolute_url, my reaction was, "What were they thinking!". Why does the model have any knowledge about it's presentation? What if that very same model object is used for two completely separate purposes in two different applications? Then I realized that this method is mainly used by the Admin application as a convenience method for creating that nice little "View on site" link. Now that finally made some sense in terms of what they were thinking. get_absolute_url is a nice little parlor trick for the Admin application, that then got subverted for inappropriate uses. In our main application, it has been mandated not to use get_absolute_url ever. We have in place a mechanism to allow the view layers to generate a url for a given object. +1 for deprecating. Pat McNerthney ClearPoint Metrics, Inc. Yuri Baburov wrote: > Hi Jacob, > > how about my kind of patch -- deprecation and removal of the feature? :) > > On Mon, Sep 14, 2009 at 8:24 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > >> Hi guys -- >> >> Ya know, this conversation is going in circles, and arguing over >> increasingly trivial details. As always, our policy is that the person >> who builds the bikeshed gets to decide which color it is, so I'd >> suggest we all stop writing email and start writing Python now. Work >> up a patch, and then let's discuss from there. >> > > --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
