ah ha! a bug in my app's db.py was preventing dev_appserver.py from calling my task url... sensitive chap. these subtly differences between web2py, dev_appserver and GAE are frustrating - I'll be happier when it's all in the cloud :)
On 2 June 2011 15:28, Carl Roach <[email protected]> wrote: > thanks for the feedback. > my task is called correctly when I manually "Run" it from > http://localhost:8080/_ah/admin/tasks?queue=default > > I've given the task a name (to make it unique) using a mixture of a-z0-9- > > The fact that dev_appserver is failing to call the URL correctly / URL is > failing to call web2py code is annoying. On GAE it works fine. > > > On 2 June 2011 15:25, howesc <[email protected]> wrote: > >> taskqueue is no longer a labs feature, but a trunk feature on GAE, so use: >> >> from google.appengine.api import taskqueue >> >> can you try and load the logged URL by hand in the browser? It should >> follow the same URL processing and i have not had to add special routes.py >> or app.yaml to make it work. >> >> cfh >> > >
