Just following up... If you use the query string option, you don't need to know the current url, you can just do this:
{% if has_previous %} <a href="?page={{ previous }}">Previous</a> {% endif %} And the browser fills in the current url path minus any query string and that just appends to it, which is kind of nice. I like the clean URL of: /url/page2/ But I like how this works better in the template: /url/?page=2 Unless I'm missing something which I thought I might be. Perhaps the pagination stuff could add support for building URLs for you in either case and add "prev_url" and "next_url" to the context? Then either way is a no brainer for template authors. -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---