Rq

Latest version: v2.3.1

Safety actively analyzes 724004 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 19 of 21

0.3.7

Not secure
(February 26th, 2013)

- Fixed bug where workers would not execute builtin functions properly.

0.3.6

Not secure
(February 18th, 2013)

- Worker registrations now expire. This should prevent `rqinfo` from reporting
about ghosted workers. (Thanks, yaniv-aknin!)

- `rqworker` will automatically clean up ghosted worker registrations from
pre-0.3.6 runs.

- `rqworker` grew a `-q` flag, to be more silent (only warnings/errors are shown)

0.3.5

Not secure
(February 6th, 2013)

- `ended_at` is now recorded for normally finished jobs, too. (Previously only
for failed jobs.)

- Adds support for both `Redis` and `StrictRedis` connection types

- Makes `StrictRedis` the default connection type if none is explicitly provided

0.3.4

Not secure
(January 23rd, 2013)

- Restore compatibility with Python 2.6.

0.3.3

Not secure
(January 18th, 2013)

- Fix bug where work was lost due to silently ignored unpickle errors.

- Jobs can now access the current `Job` instance from within. Relevant
documentation [here](http://python-rq.org/docs/jobs/).

- Custom properties can be set by modifying the `job.meta` dict. Relevant
documentation [here](http://python-rq.org/docs/jobs/).

- Custom properties can be set by modifying the `job.meta` dict. Relevant
documentation [here](http://python-rq.org/docs/jobs/).

- `rqworker` now has an optional `--password` flag.

- Remove `logbook` dependency (in favor of `logging`)

0.3.2

Not secure
(September 3rd, 2012)

- Fixes broken `rqinfo` command.

- Improve compatibility with Python < 2.7.

Page 19 of 21

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.