Hi George,
The behaviour for {% url %} has since been changed when used with
a RequestContext. It will now default to the current namespace when
one is available. This change will be available in 1.9.
This change doesn't cover the thread-local storage for calls to reverse(),
or for {% url %}
That's exactly what I'm thinking about. Unfortunately, it's not brought to
the attention among Django developers so far.
On Tuesday, 20 May 2014 02:01:55 UTC-6, Tai Lee wrote:
>
> Right now it seems that for a generic app to support the possibility of
> being installed in a URLconf with a namesp
Right now it seems that for a generic app to support the possibility of
being installed in a URLconf with a namespace, the app author will need to
take care to explicitly define a `current_app` for every call to
`reverse()`, `TemplateResponse`, `RequestContext`, `Context` and `{% url
%}`.
Djan
