I'm a bit confused by finding a process that works for both the dev
server and mod_python.
Mod_python uses a 'trigger' word to know to pass serving of that stuff
by Django. So URL's with /mysite/ leading them get handled by
Django. But it seems that the urls.py then gets the URL without the
leading /mysite/ element.
The dev server however would pass along the full URL. So if I have a
URL that I am targetting which is /mysite/soStuff
my URL conf will service the request when using the dev server with:
(r'^mysite/doStuff/$', 'mysite.project.views.doSomething'),
whereas the same click handled by mod_python will need an URL conf:
(r'^doStuff/$', 'mysite.project.views.doSomething'),
To make me more confused, there is a cryptic line in the documentation
that doesn't make sense to me:
Django's URLconfs won't trim the "/mysite/" -- they get passed the
full URL
That seems to conflict with the actual behaviour described above, no?
Anyway, I don't know how I can make my urls.py work for both dev-
server and mod_python, short of having two url-confs for every URL,
which I am awkwardly doing for now. I must be missing something
here, so your help would be appreciated..
-Ross
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
