I don’t know how long this feature has been part of Django but as the following article shows, it can be achieved as follows in the view: from django.core.urlresolvers import resolve current_url = resolve(request.path_info).url_name If you need that in every template, writing a template request can be appropriate. Edit: APPLYING NEW DJANGO UPDATE Following the … Read more
No. It is just that django gives you the option to name your views in case you need to refer to them from your code, or your templates. This is useful and good practice because you avoid hardcoding urls on your code or inside your templates. Even if you change the actual url, you don’t … Read more
You can’t capture GET parameters in the url confs, so your method is correct. I generally prefer string formatting but it’s the same thing. “%s?next=%s” % (reverse(name), reverse(redirect)) http://docs.djangoproject.com/en/dev/topics/http/urls/#what-the-urlconf-searches-against The URLconf searches against the requested URL, as a normal Python string. This does not include GET or POST parameters, or the domain name.
I don’t know how long this feature has been part of Django but as the following article shows, it can be achieved as follows in the view: from django.core.urlresolvers import resolve current_url = resolve(request.path_info).url_name If you need that in every template, writing a template request can be appropriate. Edit: APPLYING NEW DJANGO UPDATE Following the … Read more