im_task

This package contains the @task function, for decorating python functions to be appengine tasks.

Install

Use the python package for this library. You can find the package online here.

Change to your Python App Engine project's root folder and do the following:

pip install im_task --target lib

Or add it to your requirements.txt. You'll also need to set up vendoring, see app engine vendoring instructions here.

@task

This decorator function is designed to be used as a replacement for deferred.

Configuring @task

This bit needs a rewrite. Note that this library doesn't provide utilities for frameworks (eg: flask, webapp2), for those you'll want the following packages:

• im_task_flask
• im_task_webapp2

Importing task

You can import task into your modules like this:

from im_task import task

Using task as a decorator

You can take any function and make it run in a separate task, like this:

@task
def myfunction():
  ... do stuff ... 

Just call the function normally, eg:

myfunction()

You can use @task on any function, including nested functions, recursive functions, recursive nested functions, the sky is the limit. This is possible because of use of yccloudpickle as the underlying serialisation library.

Your function can also have arguments, including other functions:

def myouterfunction(mapf):

    @task
    def myinnerfunction(objects):
    	for object in objects:
    		mapf(object)
    		
    ...get some list of lists of objects... 
	for objects in objectslist:
		myinnerfunction(objects)
		
def dosomethingwithobject(object):
	... do something with an object ...		

myouterfunction(dosomethingwithobject)

The functions and arguments are being serialised and deserialised for you behind the scenes.

When enqueuing a background task, the App Engine Task and TaskQueue libraries can take a set of parameters. You can pass these to the decorator:

@task(queue="myqueue", countdown=5)
def anotherfunction():
  ... do stuff ... 

Details of the arguments allowed to Tasks are available here, under class google.appengine.api.taskqueue.Task(payload=None, **kwargs). The task decorator supports a couple of extra ones, detailed below.

Using task as a factory

You can also use task to decorate a function on the fly, like this:

def somefunction(a, b):
  ... does something ...
  
somefunctionintask = task(somefunction, queue="myqueue")

Then you can call the function returned by task when you are ready:

somefunctionintask(1, 2)

You could do both of these steps at once, too:

task(somefunction, queue="myqueue")(1, 2)

transactional

Pass transactional=True to have your task launch transactionally. eg:

@task(transactional=True)
def myserioustransactionaltask():
  ...

includeheaders

If you'd like access to headers in your function (a dictionary of headers passed to your task, it's a web request after all), set includeheaders=True in your call to @task. You'll also need to accept the headers argument in your function.

@task(includeheaders=True)
def myfunctionwithheaders(amount, headers):
    ... stuff ...
    
myfunctionwithheaders(10)

App Engine passes useful information to your task in headers, for example X-Appengine-TaskRetryCount.

other bits

When using deferred, all your calls are logged as /_ah/queue/deferred. But @task uses a url of the form /_ah/task/<module>/<function>, eg:

/_ah/task/mymodule/somefunction

which makes debugging a lot easier.