rq v0.3.1 Release Notes

  • (August 30th, 2012)

    • .enqueue() now takes a result_ttl keyword argument that can be used to change the expiration time of results.

    • Queue constructor now takes an optional async=False argument to bypass the worker (for testing purposes).

    • ๐Ÿ‘ท Jobs now carry status information. To get job status information, like whether a job is queued, finished, or failed, use the property status, or one of the new boolean accessor properties is_queued, is_finished or is_failed.

    • ๐Ÿ‘ท Jobs return values are always stored explicitly, even if they have to explicit return value or return None (with given TTL of course). This makes it possible to distinguish between a job that explicitly returned None and a job that isn't finished yet (see status property).

    • ๐Ÿ”ง Custom exception handlers can now be configured in addition to, or to fully replace, moving failed jobs to the failed queue. Relevant documentation here and here.

    • ๐Ÿ”ง rqworker now supports passing in configuration files instead of the many command line options: rqworker -c settings will source settings.py.

    • ๐Ÿ‘ท rqworker now supports one-flag setup to enable Sentry as its exception handler: rqworker --sentry-dsn="http://public:[email protected]/1" Alternatively, you can use a settings file and configure SENTRY_DSN = 'http://public:[email protected]/1' instead.