Testing Push Queues in the Development Server

This API is supported for first-generation runtimes and can be used when upgrading to corresponding second-generation runtimes. If you are updating to the App Engine Python 3 runtime, refer to the migration guide to learn about your migration options for legacy bundled services.

This page describes some limitations with using the local development server (dev_appserver) to test push queues in your application. In most respects, you set up your queues and tasks just as you would to run them in the App Engine production environment, but there are some differences:

• The development server doesn't respect the rate and bucket-size attributes of your queues. As a result, tasks are executed as close to their ETA as possible. Setting a rate of 0 doesn't prevent tasks from being executed automatically.
• The development server doesn't preserve queue state across restarts.

Important:

• Before running the local development server, follow the setup instructions. Regardless of your app's runtime or language version, you must run dev_appserver.py with Python 3 and set the CLOUDSDK_DEVAPPSERVER_PYTHON environment variable in your shell to the path of your Python 2 interpreter.
• The dev_appserver tool does not support development of Python 3 apps on Windows.

To prevent push tasks from running in the development server at all, use the following command:

python2 DEVAPPSERVER_ROOT/google_appengine/dev_appserver.py --enable_task_running no

Replace DEVAPPSERVER_ROOT with the path to the folder where you extract the archived version of devapp_server.py. For more information about downloading and using the archived version of dev_appserver.py, see Using the local development server.

For more information about devapp_server.py command options, see Local development server options.