On 24 sep, 13:03, tsmets <[EMAIL PROTECTED]> wrote:
> I am refactoring my URL matching configuration file and I get this :
> [snip]
> Page not found (404)
> Request Method: GET
> Request URL: http://localhost:8000/followDeploys/viewDeployed/xxx
>
> Using the URLconf defined in customer.urls, Django tried these URL
> patterns, in this order:
>
> 1. ^followDeploys/ ^viewDeployed/(?P<appAcronym>[^a-z][a-z0-9][a-
> z0-9])
Are you sure the last part (<appAcronym) is ok ??? "[^a-z]" means
"everything *but* a character in range a-z".
> 2. ^admin/(.*)
>
> The current URL, followDeploys/viewDeployed/xxx, didn't match any of
> these.
> [/snip]
>
> Now there is an extra space in the first matching URL pattern.
AFAICT, this 'extra space' is in the error page display only, not in
the pattern effectively used for matching - I can see similar things
here with patterns that I know are ok and working.
You didn't specify the effective value of the appAcronym part you used
for your tests, but it won't match anything starting with a lowercase
letter.
My 2 cents...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
