2012-07-23 10:01:35 +00:00
|
|
|
### 0.3.0
|
2012-07-20 12:50:23 +00:00
|
|
|
(not released)
|
|
|
|
|
2012-07-23 10:01:35 +00:00
|
|
|
- Removes the possible ambiguity of passing in a `timeout` argument to
|
|
|
|
`.enqueue()`. Instead, now use the `.enqueue_call()` method.
|
2012-07-20 12:50:23 +00:00
|
|
|
|
|
|
|
|
2012-07-20 12:49:18 +00:00
|
|
|
### 0.2.1
|
|
|
|
(July 20th, 2012)
|
2012-07-18 12:43:28 +00:00
|
|
|
|
2012-07-20 12:26:05 +00:00
|
|
|
- Fix important bug where result data wasn't restored from Redis correctly
|
|
|
|
(affected non-string results only).
|
|
|
|
|
2012-07-18 12:43:28 +00:00
|
|
|
|
2012-07-18 12:42:26 +00:00
|
|
|
### 0.2.0
|
|
|
|
(July 18th, 2012)
|
|
|
|
|
|
|
|
- `q.enqueue()` accepts instance methods now, too. Objects will be pickle'd
|
|
|
|
along with the instance method, so beware.
|
|
|
|
- `q.enqueue()` accepts string specification of functions now, too. Example:
|
|
|
|
`q.enqueue("my.math.lib.fibonacci", 5)`. Useful if the worker and the
|
|
|
|
submitter of work don't share code bases.
|
|
|
|
- Job can be assigned custom attrs and they will be pickle'd along with the
|
|
|
|
rest of the job's attrs. Can be used when writing RQ extensions.
|
|
|
|
- Workers can now accept explicit connections, like Queues.
|
|
|
|
- Various bug fixes.
|
2012-05-20 14:09:57 +00:00
|
|
|
|
|
|
|
|
2012-05-15 06:38:10 +00:00
|
|
|
### 0.1.2
|
|
|
|
(May 15, 2012)
|
|
|
|
|
|
|
|
- Fix broken PyPI deployment.
|
|
|
|
|
|
|
|
|
2012-05-14 06:41:56 +00:00
|
|
|
### 0.1.1
|
|
|
|
(May 14, 2012)
|
|
|
|
|
|
|
|
- Thread-safety by using context locals
|
|
|
|
- Register scripts as console_scripts, for better portability
|
|
|
|
- Various bugfixes.
|
|
|
|
|
|
|
|
|
|
|
|
### 0.1.0:
|
|
|
|
(March 28, 2012)
|
|
|
|
|
|
|
|
- Initially released version.
|