# Not particularly clever, but in a Django request context you could
# argue that "//" == "//" == "/" and change the url pattern logic
# appropriately.
Or just remove all leading slashes from any URLconf entry's regex.
--
Jonathan Daugherty
http://www.parsed.org
On 12 Dec 2005, at 3:20, pbx wrote:
I thought someone else might have a more clever approach.
Not particularly clever, but in a Django request context you could
argue that "//" == "//" == "/" and change the url pattern logic
appropriately.
Afternoon
This is a minor nit, but:
> Using the URLconf defined in foo.urls, Django tried these URL patterns, in
> this order:
>
>1. ^admin/
>2. ^/$
>
> The current URL, /, didn't match any of these.
Now, *we* know that there's an implicit "/" at the beginning of those
rules (as the docs say, "Th
