On Mar 28, 2006, at 8:55 AM, pbx wrote: > I think rolling functionality similar to ABSOLUTE_URL_OVERRIDES into > URLconfs is the way to go. As others have pointed out, > get_absolute_url() doesn't cover enough ground and creates unnecessary > coupling. > > Simon expresses it well here: > > http://groups.google.com/group/django-developers/msg/ > 98ee1a543c40e123
As far as I'm concerned, the problem has always been one of syntax and simplicity. Obviously the model is the wrong place to put a URL for all the reasons discussed, but you can't beat it for simplicity. I've tried a few times to come up with a solution that's both "correct" and just as simple, and each time I've failed. As far as I'm concerned, if someone can come up with a way to do this that's stupidly simple then I'm all for a change, but at the same time get_absolute_url() is a wart I'm willing to live with. Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
