Re: Reversing URL for a view with namespaces

2009-11-02 Thread Tai Lee
Speaking of the ways in which a namespace can be specified or provided, #11642 might be relevant here. http://code.djangoproject.com/ticket/11642 It feels a little cumbersome to me to require users to either manually specify a namespace or import a different object (than just the usual urls modu

Re: Reversing URL for a view with namespaces

2009-11-01 Thread Russell Keith-Magee
On Mon, Nov 2, 2009 at 5:44 AM, Ivan Sagalaev wrote: > > Ivan Sagalaev wrote: >> Ahha! This is the catch I was missing. So in order for an app to place >> itself generally in the "namespace-aware" category it should define a >> function that will return a triple of (patterns, app_namespace, >> in

Re: Reversing URL for a view with namespaces

2009-11-01 Thread Ivan Sagalaev
Ivan Sagalaev wrote: > Ahha! This is the catch I was missing. So in order for an app to place > itself generally in the "namespace-aware" category it should define a > function that will return a triple of (patterns, app_namespace, > instance_namespace) and document it as the only way of includ

Re: Reversing URL for a view with namespaces

2009-11-01 Thread Ivan Sagalaev
Russell Keith-Magee wrote: > Apologies for taking so long to get back to you on this. No problem :-) Have busy schedule myself :-) > For this last case - building a new app that you want to be namespace > aware - I think the Django admin already implements the model that > needs to be followed h

Re: Reversing URL for a view with namespaces

2009-10-31 Thread Russell Keith-Magee
On Tue, Oct 20, 2009 at 11:38 PM, Ivan Sagalaev wrote: > > Russell Keith-Magee wrote: >> On the 'missing something' front, reverse() now takes a 'current_app' >> argument that gives context to the app lookup, which resolves the >> ambiguity from the point of view of the reverse() function. > > I

Re: Reversing URL for a view with namespaces

2009-10-20 Thread Ivan Sagalaev
Russell Keith-Magee wrote: > On the 'missing something' front, reverse() now takes a 'current_app' > argument that gives context to the app lookup, which resolves the > ambiguity from the point of view of the reverse() function. I saw this one. It doesn't work in this case exactly beacuse of this

Re: Reversing URL for a view with namespaces

2009-10-20 Thread Russell Keith-Magee
On Tue, Oct 20, 2009 at 5:34 AM, Ivan Sagalaev wrote: > > Hello! > > I've just stumbled upon a difficult to understand problem. I have an app >  that has an urlconf which is included in a project under a namespace: > >     (r'^blog/', include('app.urls', namespace='blog')), > > This namespace all

Reversing URL for a view with namespaces

2009-10-19 Thread Ivan Sagalaev
Hello! I've just stumbled upon a difficult to understand problem. I have an app that has an urlconf which is included in a project under a namespace: (r'^blog/', include('app.urls', namespace='blog')), This namespace allows things like {% url blog:article ... %} which is very nice. But