(part 2 of 2)
I'd suggest to use the [named [URL](https://docs.djangoproject.com/en/1.5/topics/http/urls/#naming-url-patterns)  feature of Django instead of specifying the path to the actual view in the url template tag.

The former is possibly more future-proof (there is a chance the latter gets deprecated at some point).

As graphite-web is still compatible with Django 1.4 this means `{% load url from future %}` needs to be used at the top of every template that uses such tag (https://docs.djangoproject.com/en/1.4/ref/templates/builtins/#url)

The modifications proposed in this PR work so perhaps the above suggestion this can be implemented in a different commit once it lands.