Hi, To further clarify, you must _always_ include an app.yaml file with your Google App Engine app - this is the way our system knows how to serve your application, which URLs to map to which scripts, and which files are static files. This is true for both Django and non-Django users alike.
urls.py is the Django way to map scripts to URLs. If you are using Django, you would just map all requests in the app.yaml to the main function (as Alexander described), and have Django further route the request. -Marzia On Wed, Jan 28, 2009 at 9:38 AM, Alexander Kojevnikov <[email protected]> wrote: > > If you use app-engine-patch to run Django, you should add this at the > bottom of your app.yaml: > > - url: /.* > script: common/appenginepatch/main.py > > The rest of your app.yaml is for static files. And urls.py is for all > non-static handlers. > > On Jan 28, 9:22 pm, arnie <[email protected]> wrote: >> What is the difference between urls.py and app.yaml? >> I think If we are using the django web framework instead of web app >> framework from GAE SDK then we need to use urls.py, is this right? >> Any other difference between the two? >> Thanks >> Arnie > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
