Hi Nowell,
My apologies for the lack of action on this -- I've been really busy
at work over the last month or so. I'm finally coming up for air, and
this ticket is high on my list of things to look at.
The patch itself looks like it's in pretty good shape; I just need to
pick apart the logic to
Hey Russ,
Is there anything I should do to get http://code.djangoproject.com/ticket/13922
into RFC state? Let me know if you feel that the existing patch needs
any work, or better docs.
Thanks!
Nowell
On Jul 10, 4:35 am, Russell Keith-Magee
wrote:
> On Fri, Jul 9, 2010 at 1:50 PM, Nowell Strite
Hey Nate,
This actually doesn't touch handling lazy reversing of urls, this
deals strictly with enhancing the result of the resolve(...) function
to provide more detail than just func, args, kwargs.
Nowell
On Jul 12, 9:57 am, Nate wrote:
> If I'm not mistaken, this sort of lazy url reversing co
If I'm not mistaken, this sort of lazy url reversing could make it
possible to reverse URLs in settings, which has effect upon issues
such as the following:
http://groups.google.com/group/django-developers/browse_thread/thread/fa3661888716f940
Is that correct?
On Jul 11, 11:02 am, Nowell Strite
Sounds great Russ. I have created a ticket for this issue:
http://code.djangoproject.com/ticket/13922
Once you do a tear-down, and if things look good, let me know and I'll
start taking a stab at documentation.
Thanks!
Nowell
On Jul 10, 4:35 am, Russell Keith-Magee
wrote:
> On Fri, Jul 9, 2010
On Fri, Jul 9, 2010 at 1:50 PM, Nowell Strite wrote:
> When Django 1.1 was released URLs gained the ability to be nested with
> namespaces by adding "app_name" and "namespace" attributes to the
> include(...) functions within urls.py. The reverse(...) function was
> updated to allow you to specify
When Django 1.1 was released URLs gained the ability to be nested with
namespaces by adding "app_name" and "namespace" attributes to the
include(...) functions within urls.py. The reverse(...) function was
updated to allow you to specify namespace and current_app when
resolving URLs, however, we ne
