On 9/20/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> My initial reaction to the problem was to think about adding an 'app
> prefix' when you deploy an app, much like a form prefix, that is
> injected into the template context to affect the resolution of {% url
> %} tags. However, thinking about the implementation and consequences
> of such a change this early on a Friday morning is making my brain
> hurt.*Sigh* after thinking about it briefly, I don't see any obvious or easy solutions either. I think I'm going to file a ticket about the url tag and multiple sites, and when I merge newforms-admin next, I'm not going to integrate this particular changeset. If anyone sees any possible alternatives that can be implemented quickly (and thus, not hold up a merge) please speak up. Joseph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
