On Sun, 2008-10-05 at 12:30 +0300, Erik Allik wrote:
> Malcolm,
>
> what if I did the from django.core.urlresolvers import reverse part in
> the function itself that gets called?
>
> def my_flatpage_url(o):
> from django.core.urlresolvers import reverse
> return '%s%s' % (reverse('my-site-index'), o.url)
>
> ABSOLUTE_URL_OVERRIDES = {
> 'flatpages.flatpage': my_flatpage_url,
> }
>
> That wouldn't introduce a chicken-and-egg problem, would it?
*sigh* As I mentioned earlier, if it works by accident now, then that's
fine, but don't come crying if it stops working in the future because we
happen to change when we evaluate ABSOLUTE_URL_OVERRIDES to somewhat
earlier than you expected or something. It's simply far too
time-consuming, fiddly and generally counter-productive to try and play
games with which parts of Django you can use in settings. Don't do that.
It seems like people are determined to do dangerous things just because
they can. That's fine. This is professional computer science and we're
all adults. But using ABSOLUTE_URL_OVERRIDES in a way that requires
access to your URL configuration would suggest to me that you're abusing
the notion and should probably come up with an alternate solution in any
case.
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
