I'd much rather have this information come from the current request vs. coming from settings. Relying on the Site is particularly annoying. I like the implementation of build_absolute_uri() in django.http.HttpRequest. The hard part is getting the request object to a place where it's usable by models without introduction global state.
Mike On Mon, Dec 7, 2009 at 2:43 PM, Simon Willison <si...@simonwillison.net> wrote: > This made it to the 1.2 feature list: > > http://code.djangoproject.com/wiki/ReplacingGetAbsoluteUrl > > If we want this in 1.2, it could be as simple as merging the get_url / > get_url_path methods in to the base Model class, rolling a few unit > tests and writing some documentation. It feels like we should discuss > it a bit first though - the proposal hasn't really seen much > discussion since it was originally put together back in September last > year. > > Cheers, > > Simon > > -- > > 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. > > > -- 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.
